Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eed8cbe598b0b3d48ef3abcdb56bb8175e130621b12ff6255cbece0404c0ea5f

Tx prefix hash: 2b44cf6ae872f5583137e5d1addcef053e0be5ed549b92ca369011b75c2ea8b6
Tx public key: 679dd28cd3c1ecea38bfe901308d5461e3e6063e70827e9c5fcecad9ef92d659
Timestamp: 1703862400 Timestamp [UCT]: 2023-12-29 15:06:40 Age [y:d:h:m:s]: 01:110:18:13:13
Block: 923764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340282 RingCT/type: yes/0
Extra: 01679dd28cd3c1ecea38bfe901308d5461e3e6063e70827e9c5fcecad9ef92d6590211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf14bef72dcbfe734a617981a3c9e0c9a5a886b13996a2c524d12bb86b219ed1 0.600000000000 1381500 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": 923774, "vin": [ { "gen": { "height": 923764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf14bef72dcbfe734a617981a3c9e0c9a5a886b13996a2c524d12bb86b219ed1" } } ], "extra": [ 1, 103, 157, 210, 140, 211, 193, 236, 234, 56, 191, 233, 1, 48, 141, 84, 97, 227, 230, 6, 62, 112, 130, 126, 156, 95, 206, 202, 217, 239, 146, 214, 89, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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