Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1cb5d4cc6f505efccc434df78203b8b4d8ee9e5db174ee8ccd0aa9288d472ec

Tx prefix hash: cdb17be8088cc4dccc7295e9c4c4aec8d14f0baa2b06c0464c8e75fbb35f23e1
Tx public key: 1d1a4c322d74ea57dbe9e91f0d01b19266d48e11473df768f137693d2c66eb5d
Timestamp: 1761526128 Timestamp [UCT]: 2025-10-27 00:48:48 Age [y:d:h:m:s]: 00:013:23:37:47
Block: 1398710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10010 RingCT/type: yes/0
Extra: 011d1a4c322d74ea57dbe9e91f0d01b19266d48e11473df768f137693d2c66eb5d02110000000825a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cb882a765fb6debaf850da64796189f320976def38cfab0492fd1c065fc8e0b 0.600000000000 1887011 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": 1398720, "vin": [ { "gen": { "height": 1398710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cb882a765fb6debaf850da64796189f320976def38cfab0492fd1c065fc8e0b" } } ], "extra": [ 1, 29, 26, 76, 50, 45, 116, 234, 87, 219, 233, 233, 31, 13, 1, 177, 146, 102, 212, 142, 17, 71, 61, 247, 104, 241, 55, 105, 61, 44, 102, 235, 93, 2, 17, 0, 0, 0, 8, 37, 163, 90, 15, 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