Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65c6f24c17f11d103397deccdd47b4deddd3f4704b1bbcdd7efb8bca9a41b83c

Tx prefix hash: 81389f5c3da72d060037c9858602d29c112271701ff4103cdaee4bc58f52f4a6
Tx public key: 3bf32550086385efe66e83690b19106fdbd2c4bb5a8ddbadbb5d33e3c6fe46e3
Timestamp: 1708206852 Timestamp [UCT]: 2024-02-17 21:54:12 Age [y:d:h:m:s]: 00:341:09:22:03
Block: 959778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244350 RingCT/type: yes/0
Extra: 013bf32550086385efe66e83690b19106fdbd2c4bb5a8ddbadbb5d33e3c6fe46e302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30d3a3f42a1f18130bfd92ec03686a729e2fb68b800d2a42709a120c5d0c9a1c 0.600000000000 1419331 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": 959788, "vin": [ { "gen": { "height": 959778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30d3a3f42a1f18130bfd92ec03686a729e2fb68b800d2a42709a120c5d0c9a1c" } } ], "extra": [ 1, 59, 243, 37, 80, 8, 99, 133, 239, 230, 110, 131, 105, 11, 25, 16, 111, 219, 210, 196, 187, 90, 141, 219, 173, 187, 93, 51, 227, 198, 254, 70, 227, 2, 17, 0, 0, 0, 1, 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