Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bf6615a061bb5503a84d2e314ce9f4298b615f7f7c4b92b27bb2d47513d0d7d

Tx prefix hash: b7908aa82d753044fca828492d8768cda1cfb9f76794a40754e17b5218149690
Tx public key: 0c49cb7b0a62f6b584dac7af92f9cbb505bcfb0dfd3d5b8ac6b14afaf4d735e9
Timestamp: 1712632396 Timestamp [UCT]: 2024-04-09 03:13:16 Age [y:d:h:m:s]: 00:276:09:50:46
Block: 996445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197884 RingCT/type: yes/0
Extra: 010c49cb7b0a62f6b584dac7af92f9cbb505bcfb0dfd3d5b8ac6b14afaf4d735e902110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54f050371679cae05c322ad57a11a185ef3d4a5b6677d22524f722788bf70d30 0.600000000000 1456863 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": 996455, "vin": [ { "gen": { "height": 996445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54f050371679cae05c322ad57a11a185ef3d4a5b6677d22524f722788bf70d30" } } ], "extra": [ 1, 12, 73, 203, 123, 10, 98, 246, 181, 132, 218, 199, 175, 146, 249, 203, 181, 5, 188, 251, 13, 253, 61, 91, 138, 198, 177, 74, 250, 244, 215, 53, 233, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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