Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b2446667480c0b7396d4b9af5ac9f8491d350a7cc46420413edcc7c77b59a19

Tx prefix hash: 148ad30fee423c1c8ce8eeddbc8f34104c736dc8db48b33f19ecd7e9eaf822a6
Tx public key: 816a7ad7ec29c6fe677ec8909e079d4907c887e905d05aed66a38d0e006f5431
Timestamp: 1710899840 Timestamp [UCT]: 2024-03-20 01:57:20 Age [y:d:h:m:s]: 01:235:07:19:42
Block: 982129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426853 RingCT/type: yes/0
Extra: 01816a7ad7ec29c6fe677ec8909e079d4907c887e905d05aed66a38d0e006f54310211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83bba6880c9e288a88e5f4bbd3dcb4d10b26e456c9b135bcc3296591b3d213cd 0.600000000000 1442234 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": 982139, "vin": [ { "gen": { "height": 982129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83bba6880c9e288a88e5f4bbd3dcb4d10b26e456c9b135bcc3296591b3d213cd" } } ], "extra": [ 1, 129, 106, 122, 215, 236, 41, 198, 254, 103, 126, 200, 144, 158, 7, 157, 73, 7, 200, 135, 233, 5, 208, 90, 237, 102, 163, 141, 14, 0, 111, 84, 49, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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