Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d9d2fee9549c3033d306336eee79d80ceb765d828e6efb0d955031a58ca92da

Tx prefix hash: 544bc903efa3a4c5f31c0796690f19519fa305424d48c65b322cfb30d6bbd793
Tx public key: d985d0ff9f5f4a3c2cc195ef8fff98e781a40934c0973483985a4eaaa790de79
Timestamp: 1735442864 Timestamp [UCT]: 2024-12-29 03:27:44 Age [y:d:h:m:s]: 00:311:03:16:25
Block: 1185449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219872 RingCT/type: yes/0
Extra: 01d985d0ff9f5f4a3c2cc195ef8fff98e781a40934c0973483985a4eaaa790de79021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3a9d61aa35625efa8f88c1b524d6cbda853e4bdf76385c61e1eea0d5552657c 0.600000000000 1671920 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": 1185459, "vin": [ { "gen": { "height": 1185449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3a9d61aa35625efa8f88c1b524d6cbda853e4bdf76385c61e1eea0d5552657c" } } ], "extra": [ 1, 217, 133, 208, 255, 159, 95, 74, 60, 44, 193, 149, 239, 143, 255, 152, 231, 129, 164, 9, 52, 192, 151, 52, 131, 152, 90, 78, 170, 167, 144, 222, 121, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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