Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a2c77f6198822484407db14cbcd7a9be804a68059a63217c51d310559fa5500

Tx prefix hash: 9924fc5079a3aa1f3e2c57f936b93b0b7914694c50fd61aced70bce5c7b1c315
Tx public key: 8e3e6c07197e4052d6b5f44c0d52d0103e429dfa94163cb4f55a43d9fbb7e679
Timestamp: 1714903252 Timestamp [UCT]: 2024-05-05 10:00:52 Age [y:d:h:m:s]: 00:335:17:27:57
Block: 1015314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239968 RingCT/type: yes/0
Extra: 018e3e6c07197e4052d6b5f44c0d52d0103e429dfa94163cb4f55a43d9fbb7e67902110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77f2f1a5809305f0250b20c50fae8a403e0b1949be4df2ed4ab78a962a091109 0.600000000000 1478641 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": 1015324, "vin": [ { "gen": { "height": 1015314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77f2f1a5809305f0250b20c50fae8a403e0b1949be4df2ed4ab78a962a091109" } } ], "extra": [ 1, 142, 62, 108, 7, 25, 126, 64, 82, 214, 181, 244, 76, 13, 82, 208, 16, 62, 66, 157, 250, 148, 22, 60, 180, 245, 90, 67, 217, 251, 183, 230, 121, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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