Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e0a81c4e65ff2d9beec509cb2dc19160a8708e43869fede1635b441c572a5e4

Tx prefix hash: 4da5e83c3391690c1475eb99d523125c1698cc26bce2922365adb985a412309f
Tx public key: d0e42552b8df4e56ccd037d10db168fe125d27d4e1ced6d2b9334b893b405a90
Timestamp: 1711250512 Timestamp [UCT]: 2024-03-24 03:21:52 Age [y:d:h:m:s]: 00:245:15:02:39
Block: 985034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175826 RingCT/type: yes/0
Extra: 01d0e42552b8df4e56ccd037d10db168fe125d27d4e1ced6d2b9334b893b405a900211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1df98506d620169c2bbaebaba9144aa5f65c8f4afeab0b11a59e2b6e62878f03 0.600000000000 1445239 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": 985044, "vin": [ { "gen": { "height": 985034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1df98506d620169c2bbaebaba9144aa5f65c8f4afeab0b11a59e2b6e62878f03" } } ], "extra": [ 1, 208, 228, 37, 82, 184, 223, 78, 86, 204, 208, 55, 209, 13, 177, 104, 254, 18, 93, 39, 212, 225, 206, 214, 210, 185, 51, 75, 137, 59, 64, 90, 144, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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