Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6039477300ce2b301462b4fdf934c346f051530cb55b521aee66ccad8d02d3bd

Tx prefix hash: 469aa8734aabe7f5245c841366d7ed70e614c8f0e3ed2636f65021dd112d468d
Tx public key: f0fe41b55ed8e274dc02f6b34c57a423884b23a4b45acc35558bbe74ed6e6176
Timestamp: 1709752716 Timestamp [UCT]: 2024-03-06 19:18:36 Age [y:d:h:m:s]: 01:068:17:38:32
Block: 972609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310154 RingCT/type: yes/0
Extra: 01f0fe41b55ed8e274dc02f6b34c57a423884b23a4b45acc35558bbe74ed6e617602110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a30721c4c92035b00ba3d8c12561faf99260683e1b11de2dff7bfb0b97de9cb 0.600000000000 1432526 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": 972619, "vin": [ { "gen": { "height": 972609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a30721c4c92035b00ba3d8c12561faf99260683e1b11de2dff7bfb0b97de9cb" } } ], "extra": [ 1, 240, 254, 65, 181, 94, 216, 226, 116, 220, 2, 246, 179, 76, 87, 164, 35, 136, 75, 35, 164, 180, 90, 204, 53, 85, 139, 190, 116, 237, 110, 97, 118, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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