Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9285f7bb1b8e6d04cdfe02a5b28133c9673df66d155d537c1e007de0adf5453

Tx prefix hash: 8cc1b3511ac79be9174b33b3c920ece59425a81fde536d968f827df1afcaae79
Tx public key: 07422af0e39490485f74e26fa1f3e4e24df76b7bbdf584a0164d55d0fe28fb1b
Timestamp: 1763921703 Timestamp [UCT]: 2025-11-23 18:15:03 Age [y:d:h:m:s]: 00:004:13:00:19
Block: 1418562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3249 RingCT/type: yes/0
Extra: 0107422af0e39490485f74e26fa1f3e4e24df76b7bbdf584a0164d55d0fe28fb1b021100000009d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 636e63b41977dd516e7000dbed7fdcd1eb49e84acc677771eac8384148d53b40 0.600000000000 1907095 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": 1418572, "vin": [ { "gen": { "height": 1418562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "636e63b41977dd516e7000dbed7fdcd1eb49e84acc677771eac8384148d53b40" } } ], "extra": [ 1, 7, 66, 42, 240, 227, 148, 144, 72, 95, 116, 226, 111, 161, 243, 228, 226, 77, 247, 107, 123, 189, 245, 132, 160, 22, 77, 85, 208, 254, 40, 251, 27, 2, 17, 0, 0, 0, 9, 214, 225, 157, 124, 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