Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83941df6a80fd2624c396f2249426b290ba89299c7854939639a4fe8eaceda4b

Tx prefix hash: 23f06c6c68d59c3697c8cb59af45e2e854be27ab196c4e9edd1613fc1d92a3cc
Tx public key: 216cb5dc1dac25bf10fa625fc81676c5e51bebb4d3577451cd6ea36aa2858e8b
Timestamp: 1731322727 Timestamp [UCT]: 2024-11-11 10:58:47 Age [y:d:h:m:s]: 00:140:03:02:56
Block: 1151334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99974 RingCT/type: yes/0
Extra: 01216cb5dc1dac25bf10fa625fc81676c5e51bebb4d3577451cd6ea36aa2858e8b021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b44dfc68f00734c2e43ab30a3e823e1256650c0dd5f05184eddd6555a421e1fb 0.600000000000 1636847 of 15

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": 1151344, "vin": [ { "gen": { "height": 1151334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b44dfc68f00734c2e43ab30a3e823e1256650c0dd5f05184eddd6555a421e1fb" } } ], "extra": [ 1, 33, 108, 181, 220, 29, 172, 37, 191, 16, 250, 98, 95, 200, 22, 118, 197, 229, 27, 235, 180, 211, 87, 116, 81, 205, 110, 163, 106, 162, 133, 142, 139, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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