Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10162bdbff6a58a40a090e536b81d09104bd233b5e1304f284e222cd4443a6ac

Tx prefix hash: dc809eb1410d7e924d96ef3beaa078f42d6dd3d874ce55269c46e82126aa3ed1
Tx public key: 0e65e3d0548707e894513c83c33418af9e88eab2a988f958d9b18d1eb5cec027
Timestamp: 1709374599 Timestamp [UCT]: 2024-03-02 10:16:39 Age [y:d:h:m:s]: 01:104:20:42:22
Block: 969474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335892 RingCT/type: yes/0
Extra: 010e65e3d0548707e894513c83c33418af9e88eab2a988f958d9b18d1eb5cec0270211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54c2e4aacefe6a54de6bb9f447accb3fa41375d616d3a4b42b85fc7b677d1199 0.600000000000 1429307 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": 969484, "vin": [ { "gen": { "height": 969474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54c2e4aacefe6a54de6bb9f447accb3fa41375d616d3a4b42b85fc7b677d1199" } } ], "extra": [ 1, 14, 101, 227, 208, 84, 135, 7, 232, 148, 81, 60, 131, 195, 52, 24, 175, 158, 136, 234, 178, 169, 136, 249, 88, 217, 177, 141, 30, 181, 206, 192, 39, 2, 17, 0, 0, 0, 2, 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