Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c8da59e66d9617257ab358c54022a14d017702c278581fb41f9e4c4ea50ba2e

Tx prefix hash: 41d3285e0165012b52cd7641443b3a73330ffe68c4e88191e95cc09d5763e032
Tx public key: eafed57cced4b304ec86a9d0d9c401a5fe8de5e859fd1ef9af9cc9b826d484b1
Timestamp: 1724359264 Timestamp [UCT]: 2024-08-22 20:41:04 Age [y:d:h:m:s]: 00:231:12:03:51
Block: 1093705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165319 RingCT/type: yes/0
Extra: 01eafed57cced4b304ec86a9d0d9c401a5fe8de5e859fd1ef9af9cc9b826d484b1021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32f0a302730afa0b0dad11c29b9acd24ba86fe0ff00e22b1df255c365dba1a71 0.600000000000 1568702 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": 1093715, "vin": [ { "gen": { "height": 1093705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32f0a302730afa0b0dad11c29b9acd24ba86fe0ff00e22b1df255c365dba1a71" } } ], "extra": [ 1, 234, 254, 213, 124, 206, 212, 179, 4, 236, 134, 169, 208, 217, 196, 1, 165, 254, 141, 229, 232, 89, 253, 30, 249, 175, 156, 201, 184, 38, 212, 132, 177, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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