Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae7e3664c66fabce12ee20fb2c7b3ce15e08db19c99ad3e1f1b4ad412fc2864b

Tx prefix hash: d3c42ed73e62c30b597f81334464149e37bf4e3ef675e8cde5e503be977b61ef
Tx public key: 96afd1aed4e5f271272b556f480c3e0430b8e83b0f2b040a7ecdd6dc5a14a73b
Timestamp: 1729463474 Timestamp [UCT]: 2024-10-20 22:31:14 Age [y:d:h:m:s]: 00:143:12:27:53
Block: 1136010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102346 RingCT/type: yes/0
Extra: 0196afd1aed4e5f271272b556f480c3e0430b8e83b0f2b040a7ecdd6dc5a14a73b02110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b8e75805b318bc8026f6021bc635b98ca9588e6403ff75ef50d0bf19317cf1f 0.600000000000 1619351 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": 1136020, "vin": [ { "gen": { "height": 1136010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b8e75805b318bc8026f6021bc635b98ca9588e6403ff75ef50d0bf19317cf1f" } } ], "extra": [ 1, 150, 175, 209, 174, 212, 229, 242, 113, 39, 43, 85, 111, 72, 12, 62, 4, 48, 184, 232, 59, 15, 43, 4, 10, 126, 205, 214, 220, 90, 20, 167, 59, 2, 17, 0, 0, 0, 15, 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