Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc2de237179a272fdbdaf53bfb75b75cfd6471c54010b8e78829f1c9b25b236a

Tx prefix hash: adbe3ae394a174e862cbd738492b6f630f252df88914460e5221aa8f3bbe94c5
Tx public key: 3f5a810d62dec61a48f8003b0142f07131d80f8bdd7a3a57356299994527623e
Timestamp: 1708574145 Timestamp [UCT]: 2024-02-22 03:55:45 Age [y:d:h:m:s]: 01:261:18:09:30
Block: 962832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445825 RingCT/type: yes/0
Extra: 013f5a810d62dec61a48f8003b0142f07131d80f8bdd7a3a57356299994527623e0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b9a12b7bf425343ad3e92faf73e241fc56f8171888f49d5dd1a612467c5c0b6 0.600000000000 1422517 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": 962842, "vin": [ { "gen": { "height": 962832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b9a12b7bf425343ad3e92faf73e241fc56f8171888f49d5dd1a612467c5c0b6" } } ], "extra": [ 1, 63, 90, 129, 13, 98, 222, 198, 26, 72, 248, 0, 59, 1, 66, 240, 113, 49, 216, 15, 139, 221, 122, 58, 87, 53, 98, 153, 153, 69, 39, 98, 62, 2, 17, 0, 0, 0, 4, 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