Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b172b85844fe92983769ef3dd649a2baebb64aa75c4cce278f5906a2594c882b

Tx prefix hash: ab8debfbc9026960306225b2afb9af5e0373808aad650bbd8012a6fd95e99c27
Tx public key: 85d7a389ec1065cce8ac511b6eb5b280dc46d4fdac867ace1fd6e7e881e326f0
Timestamp: 1687496573 Timestamp [UCT]: 2023-06-23 05:02:53 Age [y:d:h:m:s]: 01:310:03:31:10
Block: 788337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482844 RingCT/type: yes/0
Extra: 0185d7a389ec1065cce8ac511b6eb5b280dc46d4fdac867ace1fd6e7e881e326f0021100000003e6d27f9c000000000000000000

1 output(s) for total of 1.499382410000 dcy

stealth address amount amount idx
00: 4e112f03c7f525b3c5de0affcd2e30d0db88feef7d2484218549d40c532e56c0 1.499382410000 1238438 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 788347, "vin": [ { "gen": { "height": 788337 } } ], "vout": [ { "amount": 1499382410, "target": { "key": "4e112f03c7f525b3c5de0affcd2e30d0db88feef7d2484218549d40c532e56c0" } } ], "extra": [ 1, 133, 215, 163, 137, 236, 16, 101, 204, 232, 172, 81, 27, 110, 181, 178, 128, 220, 70, 212, 253, 172, 134, 122, 206, 31, 214, 231, 232, 129, 227, 38, 240, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8