Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a71d393bf071b2c9543d3d895e9533e17ddb89b4a6224066ea549c97c1861c21

Tx prefix hash: b622220236b3c04629da16aef66afefacbc3df4a0a800abbf181e608d55dc557
Tx public key: e93fb18ad21de59f3e294abcb38ccef997353c8cb70d8bd25dd39c55aeaae2ca
Timestamp: 1734460334 Timestamp [UCT]: 2024-12-17 18:32:14 Age [y:d:h:m:s]: 00:110:19:25:57
Block: 1177351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78953 RingCT/type: yes/0
Extra: 01e93fb18ad21de59f3e294abcb38ccef997353c8cb70d8bd25dd39c55aeaae2ca0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d1debe45155c62b6d9b06ff01b662c739a43bef6b8d0442280e7cda4e939808 0.600000000000 1663722 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": 1177361, "vin": [ { "gen": { "height": 1177351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d1debe45155c62b6d9b06ff01b662c739a43bef6b8d0442280e7cda4e939808" } } ], "extra": [ 1, 233, 63, 177, 138, 210, 29, 229, 159, 62, 41, 74, 188, 179, 140, 206, 249, 151, 53, 60, 140, 183, 13, 139, 210, 93, 211, 156, 85, 174, 170, 226, 202, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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