Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 025208674b1336ca3b21b734217c504c2f2ebf6f27620568b6e3448be43a8a51

Tx prefix hash: ae64130ff64970b5f7a00ac78e41f40b4a5565579d1f0cb5c21fe039b46b4323
Tx public key: 0968cb0bf6d8c2c8d8a9b9624e6ee1c0ab72b149c1be85374a3535111d01aec7
Timestamp: 1723581293 Timestamp [UCT]: 2024-08-13 20:34:53 Age [y:d:h:m:s]: 00:162:03:22:48
Block: 1087247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115950 RingCT/type: yes/0
Extra: 010968cb0bf6d8c2c8d8a9b9624e6ee1c0ab72b149c1be85374a3535111d01aec7021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8c5d98fd3d53dd075d215dc7f9cb3669fb848eaeebe464e13bcb3d9d2f555b6 0.600000000000 1561854 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": 1087257, "vin": [ { "gen": { "height": 1087247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8c5d98fd3d53dd075d215dc7f9cb3669fb848eaeebe464e13bcb3d9d2f555b6" } } ], "extra": [ 1, 9, 104, 203, 11, 246, 216, 194, 200, 216, 169, 185, 98, 78, 110, 225, 192, 171, 114, 177, 73, 193, 190, 133, 55, 74, 53, 53, 17, 29, 1, 174, 199, 2, 17, 0, 0, 0, 8, 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