Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f5ee236e3c5b86edf1c2a309bab161148fde71331eb7c14c1734c61b76723ff

Tx prefix hash: b19a6c5299dd684f7618eac662b6cbf052783da3b740117dfd0babcb6419c4eb
Tx public key: 7406919b081c37f2d24f067fee44d067e86c968a47c6ea2b67557c95d8123c94
Timestamp: 1727734936 Timestamp [UCT]: 2024-09-30 22:22:16 Age [y:d:h:m:s]: 00:232:04:35:06
Block: 1121684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165787 RingCT/type: yes/0
Extra: 017406919b081c37f2d24f067fee44d067e86c968a47c6ea2b67557c95d8123c9402110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08f608de991f2bcbf5cbbb747ccfbbc7ac11b15c40573ff88ba46d286e146f61 0.600000000000 1604001 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": 1121694, "vin": [ { "gen": { "height": 1121684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08f608de991f2bcbf5cbbb747ccfbbc7ac11b15c40573ff88ba46d286e146f61" } } ], "extra": [ 1, 116, 6, 145, 155, 8, 28, 55, 242, 210, 79, 6, 127, 238, 68, 208, 103, 232, 108, 150, 138, 71, 198, 234, 43, 103, 85, 124, 149, 216, 18, 60, 148, 2, 17, 0, 0, 0, 4, 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