Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0de620667899ff312e4241ea327793fbf3ae5be2d0e3e203d16d41735bdcfb97

Tx prefix hash: 9905811de7683a222d84fe767d6d3ee7b3a8f9334cf2bba11f26b07ac1dba904
Tx public key: 4ad9a946b62039c84cc2af1e7a2270641df97974721cc80182dce314d211b32b
Timestamp: 1730038928 Timestamp [UCT]: 2024-10-27 14:22:08 Age [y:d:h:m:s]: 00:173:03:10:24
Block: 1140743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123550 RingCT/type: yes/0
Extra: 014ad9a946b62039c84cc2af1e7a2270641df97974721cc80182dce314d211b32b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57e3d3bff1eec7e1318c0de8230f79908e797593948df3e169710d6d2d61491b 0.600000000000 1624546 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": 1140753, "vin": [ { "gen": { "height": 1140743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57e3d3bff1eec7e1318c0de8230f79908e797593948df3e169710d6d2d61491b" } } ], "extra": [ 1, 74, 217, 169, 70, 182, 32, 57, 200, 76, 194, 175, 30, 122, 34, 112, 100, 29, 249, 121, 116, 114, 28, 200, 1, 130, 220, 227, 20, 210, 17, 179, 43, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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