Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1ac36b55b23abe3f934aed861dd221a4a0c62ac6b61dbd8e684ebcb43168f60

Tx prefix hash: 398cc4bae4e11569d4249d84407825fc5efe888db71d974f0f538eab3d170ebe
Tx public key: 98be0be10ce7d13520efd6909387a4d6ddfe727376f327f1b7b5e988e8d4073b
Timestamp: 1734345212 Timestamp [UCT]: 2024-12-16 10:33:32 Age [y:d:h:m:s]: 00:093:15:43:16
Block: 1176392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66722 RingCT/type: yes/0
Extra: 0198be0be10ce7d13520efd6909387a4d6ddfe727376f327f1b7b5e988e8d4073b021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ee479156a38c293fb390b274aa93f1691eba2c1d08ba1e5ba0a38a19482d2df 0.600000000000 1662723 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": 1176402, "vin": [ { "gen": { "height": 1176392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ee479156a38c293fb390b274aa93f1691eba2c1d08ba1e5ba0a38a19482d2df" } } ], "extra": [ 1, 152, 190, 11, 225, 12, 231, 209, 53, 32, 239, 214, 144, 147, 135, 164, 214, 221, 254, 114, 115, 118, 243, 39, 241, 183, 181, 233, 136, 232, 212, 7, 59, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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