Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c031d1c2c02404e5004dc430bd66328a6843f6a249f88b730207a81ad9ca292

Tx prefix hash: 65aa5325360a346dad39ac09087c1226d4cafff891cf0044a35be7fde11b2dda
Tx public key: c2d004f4a374180c09400174f01c7175f59ad681d2fdefc4f2506677e1bb15f8
Timestamp: 1633266505 Timestamp [UCT]: 2021-10-03 13:08:25 Age [y:d:h:m:s]: 03:121:09:42:39
Block: 345845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 863528 RingCT/type: yes/0
Extra: 01c2d004f4a374180c09400174f01c7175f59ad681d2fdefc4f2506677e1bb15f8021100000001a272b9cb000000000000000000

1 output(s) for total of 43.860378678000 dcy

stealth address amount amount idx
00: cad7fcea57030a0a3df2df72764cca1fb807be430dbca1aeecbbd3bcace2c6bb 43.860378678000 709367 of 0

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": 345855, "vin": [ { "gen": { "height": 345845 } } ], "vout": [ { "amount": 43860378678, "target": { "key": "cad7fcea57030a0a3df2df72764cca1fb807be430dbca1aeecbbd3bcace2c6bb" } } ], "extra": [ 1, 194, 208, 4, 244, 163, 116, 24, 12, 9, 64, 1, 116, 240, 28, 113, 117, 245, 154, 214, 129, 210, 253, 239, 196, 242, 80, 102, 119, 225, 187, 21, 248, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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