Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1160d6370e47eb6f21ea669bfa2e935a3e984c6c660892ab794684317b9a814a

Tx prefix hash: 551a4ea082160531cd03e7340eec184f4b9ac19d0e183b28283b91936f9dfbaa
Tx public key: 0c20eab80dc582f4fd6d17fb025c70856be70f9d3ff3c7b00376c9dc9bb3f3f7
Timestamp: 1730558158 Timestamp [UCT]: 2024-11-02 14:35:58 Age [y:d:h:m:s]: 00:139:17:32:59
Block: 1145003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99696 RingCT/type: yes/0
Extra: 010c20eab80dc582f4fd6d17fb025c70856be70f9d3ff3c7b00376c9dc9bb3f3f70211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12a3509c3d7daeecfb0b18d92dbed7593236872d4e22bcfb04d1a2b64c570392 0.600000000000 1629360 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": 1145013, "vin": [ { "gen": { "height": 1145003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12a3509c3d7daeecfb0b18d92dbed7593236872d4e22bcfb04d1a2b64c570392" } } ], "extra": [ 1, 12, 32, 234, 184, 13, 197, 130, 244, 253, 109, 23, 251, 2, 92, 112, 133, 107, 231, 15, 157, 63, 243, 199, 176, 3, 118, 201, 220, 155, 179, 243, 247, 2, 17, 0, 0, 0, 7, 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