Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d87cf0984146c2d3aec62195cbb3990523fe912af94a2ae1868d4a911dcd7e3

Tx prefix hash: 0ab7aad91349cc19177c10264c859e291b1deed4c12c2dee8adf0d9b87f6bf8d
Tx public key: de9c4635a73d4fb2c0ae54eef6408bfd410ba95bb1f216c00b1af56425501700
Timestamp: 1733735604 Timestamp [UCT]: 2024-12-09 09:13:24 Age [y:d:h:m:s]: 00:110:23:06:34
Block: 1171332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79084 RingCT/type: yes/0
Extra: 01de9c4635a73d4fb2c0ae54eef6408bfd410ba95bb1f216c00b1af56425501700021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a199db7b23d0f79da73a939e086254f4bdeaef3b54afcc394573743be089a49a 0.600000000000 1657073 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": 1171342, "vin": [ { "gen": { "height": 1171332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a199db7b23d0f79da73a939e086254f4bdeaef3b54afcc394573743be089a49a" } } ], "extra": [ 1, 222, 156, 70, 53, 167, 61, 79, 178, 192, 174, 84, 238, 246, 64, 139, 253, 65, 11, 169, 91, 177, 242, 22, 192, 11, 26, 245, 100, 37, 80, 23, 0, 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