Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8da007c0183df3e1cd577e41a609c1c3a7e5d7989e883133093a53785159f2b0

Tx prefix hash: cf931285c039d8a5ee594f22d2ae43fcdfb7f7a387aebfa643f678001b2ab81f
Tx public key: 921be3e0e180af425ab25b4cbc1c059d8b74c0bc4d3d51fc3ab83c484d80a2a9
Timestamp: 1741427413 Timestamp [UCT]: 2025-03-08 09:50:13 Age [y:d:h:m:s]: 00:169:09:44:14
Block: 1234738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118887 RingCT/type: yes/0
Extra: 01921be3e0e180af425ab25b4cbc1c059d8b74c0bc4d3d51fc3ab83c484d80a2a90211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4eade62c96b13d4cb7cfc9df510dfafc36a7877522d780e1bf4e380e98da05b 0.600000000000 1721673 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": 1234748, "vin": [ { "gen": { "height": 1234738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4eade62c96b13d4cb7cfc9df510dfafc36a7877522d780e1bf4e380e98da05b" } } ], "extra": [ 1, 146, 27, 227, 224, 225, 128, 175, 66, 90, 178, 91, 76, 188, 28, 5, 157, 139, 116, 192, 188, 77, 61, 81, 252, 58, 184, 60, 72, 77, 128, 162, 169, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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