Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6262b611c7718821625b80846309cc65ffd5d12f7a2de8a56b0aebccc3d6e72

Tx prefix hash: b505b80de2bbdd0d9fd915ecb9a5275237e05ec6819205b2376260e3657ca8c1
Tx public key: 7df046f7fb8481edaf79a0d3392d717eec01c649e0522e9cfbb173287497084e
Timestamp: 1715013214 Timestamp [UCT]: 2024-05-06 16:33:34 Age [y:d:h:m:s]: 01:037:14:53:39
Block: 1016216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287777 RingCT/type: yes/0
Extra: 017df046f7fb8481edaf79a0d3392d717eec01c649e0522e9cfbb173287497084e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a8020a9eba7871b9036d30e0fe9fc729f0131fe9c5910c595db5f469a8c7d02 0.600000000000 1479735 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": 1016226, "vin": [ { "gen": { "height": 1016216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a8020a9eba7871b9036d30e0fe9fc729f0131fe9c5910c595db5f469a8c7d02" } } ], "extra": [ 1, 125, 240, 70, 247, 251, 132, 129, 237, 175, 121, 160, 211, 57, 45, 113, 126, 236, 1, 198, 73, 224, 82, 46, 156, 251, 177, 115, 40, 116, 151, 8, 78, 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