Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a9cea6024153752623194037c9e9fd80c89d779d0c628af948ad4d2c83f6875

Tx prefix hash: 3b2fa9c9ea6db0cea140b9435f6036264aa75f276638144e72d30e17fea050fd
Tx public key: 0855541ae7872d4fc0a42edc785a47a497f1c5d3b74b5ba8e58d7cb440b2316e
Timestamp: 1727465438 Timestamp [UCT]: 2024-09-27 19:30:38 Age [y:d:h:m:s]: 00:105:19:09:26
Block: 1119451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75640 RingCT/type: yes/0
Extra: 010855541ae7872d4fc0a42edc785a47a497f1c5d3b74b5ba8e58d7cb440b2316e02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2e9cd2228bfbed4079f5924e05c66383633c7a512a66fc036d4c1876076f340 0.600000000000 1601010 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": 1119461, "vin": [ { "gen": { "height": 1119451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2e9cd2228bfbed4079f5924e05c66383633c7a512a66fc036d4c1876076f340" } } ], "extra": [ 1, 8, 85, 84, 26, 231, 135, 45, 79, 192, 164, 46, 220, 120, 90, 71, 164, 151, 241, 197, 211, 183, 75, 91, 168, 229, 141, 124, 180, 64, 178, 49, 110, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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