Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 320be8ee3e880a1b1ef1cfaa4aa9e0e286b0f90f04e06501c05a98e99daa7b08

Tx prefix hash: b113bd5a3dd8430033c9a5717a14f8fff001a1230f0ebd6e350150b2a82f0978
Tx public key: ed1b7af7b40df287f7b29e9effe98a034bc7395d0b7d3c23b6f125dcd830a319
Timestamp: 1704846192 Timestamp [UCT]: 2024-01-10 00:23:12 Age [y:d:h:m:s]: 01:086:09:39:44
Block: 931910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322856 RingCT/type: yes/0
Extra: 01ed1b7af7b40df287f7b29e9effe98a034bc7395d0b7d3c23b6f125dcd830a31902110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c817e04215791bc16ffe5ff8aa80f369d76805d8e51b105422af4fc32ed63e49 0.600000000000 1389816 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": 931920, "vin": [ { "gen": { "height": 931910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c817e04215791bc16ffe5ff8aa80f369d76805d8e51b105422af4fc32ed63e49" } } ], "extra": [ 1, 237, 27, 122, 247, 180, 13, 242, 135, 247, 178, 158, 158, 255, 233, 138, 3, 75, 199, 57, 93, 11, 125, 60, 35, 182, 241, 37, 220, 216, 48, 163, 25, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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