Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edd8e024f6b3e3105d913c9f65b9c6575854e0891a6d124f17079e3dcebcc96d

Tx prefix hash: 348be6d60d45ef1d66f196f686742ac00dd1e0777bb4ef23be313a8a16449b1d
Tx public key: 12596224b1d6ddd88ff986ebe552a63dfb4e448d0d5fcb75389faeb816dd4c2a
Timestamp: 1727051002 Timestamp [UCT]: 2024-09-23 00:23:22 Age [y:d:h:m:s]: 00:195:15:49:12
Block: 1116016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139644 RingCT/type: yes/0
Extra: 0112596224b1d6ddd88ff986ebe552a63dfb4e448d0d5fcb75389faeb816dd4c2a02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1dec020d24714c8b4fb86b01624c3c9d95ff803511408de119bfc1a81fdf61b0 0.600000000000 1596349 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": 1116026, "vin": [ { "gen": { "height": 1116016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dec020d24714c8b4fb86b01624c3c9d95ff803511408de119bfc1a81fdf61b0" } } ], "extra": [ 1, 18, 89, 98, 36, 177, 214, 221, 216, 143, 249, 134, 235, 229, 82, 166, 61, 251, 78, 68, 141, 13, 95, 203, 117, 56, 159, 174, 184, 22, 221, 76, 42, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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