Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f06fdedc597a07d6824af490a9dd9fcf3d438f0337923cbdeabe32d91851375c

Tx prefix hash: 9215b6e186d5a1929b2ce7a4673a9ca05364dbbbc2081cd0f87a2c384b873351
Tx public key: 4a868934ca91062ee93aee3c716da7f1ce3003fd3d589acba1cbcfd3179b2c93
Timestamp: 1737163190 Timestamp [UCT]: 2025-01-18 01:19:50 Age [y:d:h:m:s]: 00:333:11:09:46
Block: 1199695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235871 RingCT/type: yes/0
Extra: 014a868934ca91062ee93aee3c716da7f1ce3003fd3d589acba1cbcfd3179b2c930211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 651237722019be8e2cde6cfdf2d0355d9626efef29cbda9b9421ea4def1c5e3c 0.600000000000 1686328 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": 1199705, "vin": [ { "gen": { "height": 1199695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "651237722019be8e2cde6cfdf2d0355d9626efef29cbda9b9421ea4def1c5e3c" } } ], "extra": [ 1, 74, 134, 137, 52, 202, 145, 6, 46, 233, 58, 238, 60, 113, 109, 167, 241, 206, 48, 3, 253, 61, 88, 154, 203, 161, 203, 207, 211, 23, 155, 44, 147, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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