Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a241df3d2e616006d25ee781ab941083140c389d40c0bd9802397bef1510ec83

Tx prefix hash: 0fb52e21b09bb02d8f8bd28b669f072a6c763a9e3e518e13562f7447fc899516
Tx public key: e5fd8b07fa37393d578a0cfe6296437f3b1f2302e976abb26a1742d9efe8cb1f
Timestamp: 1687257744 Timestamp [UCT]: 2023-06-20 10:42:24 Age [y:d:h:m:s]: 02:142:20:40:27
Block: 786356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 621852 RingCT/type: yes/0
Extra: 01e5fd8b07fa37393d578a0cfe6296437f3b1f2302e976abb26a1742d9efe8cb1f021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.522216026000 dcy

stealth address amount amount idx
00: a5e7705fff39d23a11cee44bac2d6ccd3d1c3ad4ce58343050a0d8d730f7bdd4 1.522216026000 1236341 of 0

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": 786366, "vin": [ { "gen": { "height": 786356 } } ], "vout": [ { "amount": 1522216026, "target": { "key": "a5e7705fff39d23a11cee44bac2d6ccd3d1c3ad4ce58343050a0d8d730f7bdd4" } } ], "extra": [ 1, 229, 253, 139, 7, 250, 55, 57, 61, 87, 138, 12, 254, 98, 150, 67, 127, 59, 31, 35, 2, 233, 118, 171, 178, 106, 23, 66, 217, 239, 232, 203, 31, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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