Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c8238288ba9709e5c8cb7b313657b6353cf89e9164921be1286515dd3783eaa

Tx prefix hash: 6a4a3b14b9eaf46c07c6b83e8eea3fb9c99bc5567a04886bbbdd7245e7b2ed24
Tx public key: 8add9ad7e7232c4b0524dbeb7d3102ae9b0bf7a95507d835b4d77e5c2c07e21c
Timestamp: 1737109906 Timestamp [UCT]: 2025-01-17 10:31:46 Age [y:d:h:m:s]: 00:152:14:15:42
Block: 1199261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108747 RingCT/type: yes/0
Extra: 018add9ad7e7232c4b0524dbeb7d3102ae9b0bf7a95507d835b4d77e5c2c07e21c021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f0dc41fb42fccb25947997558b9820bf449d3f472e976f04d5d9b8069eb78b8 0.600000000000 1685890 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": 1199271, "vin": [ { "gen": { "height": 1199261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f0dc41fb42fccb25947997558b9820bf449d3f472e976f04d5d9b8069eb78b8" } } ], "extra": [ 1, 138, 221, 154, 215, 231, 35, 44, 75, 5, 36, 219, 235, 125, 49, 2, 174, 155, 11, 247, 169, 85, 7, 216, 53, 180, 215, 126, 92, 44, 7, 226, 28, 2, 17, 0, 0, 0, 8, 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