Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f5cbbdbecc080b7904e0759b338c771a37e8c9e7c59c6a80d68918e1cfe8f78

Tx prefix hash: db339efea2f7e31edaf5cc695d54c4642075b017d7a3c926aad255a8daa2007c
Tx public key: 1770d6c8b24bc89f884690e051e3beba83c894143a8f24b030cd016acd291d5e
Timestamp: 1728403928 Timestamp [UCT]: 2024-10-08 16:12:08 Age [y:d:h:m:s]: 00:156:06:23:40
Block: 1127225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111482 RingCT/type: yes/0
Extra: 011770d6c8b24bc89f884690e051e3beba83c894143a8f24b030cd016acd291d5e021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 024cf2b5350035e8f0a6249c8929e7c8c0e67a8749ad85856124b7f63afca108 0.600000000000 1610026 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": 1127235, "vin": [ { "gen": { "height": 1127225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "024cf2b5350035e8f0a6249c8929e7c8c0e67a8749ad85856124b7f63afca108" } } ], "extra": [ 1, 23, 112, 214, 200, 178, 75, 200, 159, 136, 70, 144, 224, 81, 227, 190, 186, 131, 200, 148, 20, 58, 143, 36, 176, 48, 205, 1, 106, 205, 41, 29, 94, 2, 17, 0, 0, 0, 2, 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