Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f2c482586e1aad87033b19afaa54d3adc52e2e0a77c6d32192fdefa16931fec

Tx prefix hash: 3029ecaed46d52a927d42136ce9ae56525b436e9242c37c6fcd4020cbe59c28d
Tx public key: 11f4291169865674f4dea7b16c292a5929b3c1b2b437138b7acaa6bfeb9fa93b
Timestamp: 1720494849 Timestamp [UCT]: 2024-07-09 03:14:09 Age [y:d:h:m:s]: 00:275:01:07:30
Block: 1061668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196508 RingCT/type: yes/0
Extra: 0111f4291169865674f4dea7b16c292a5929b3c1b2b437138b7acaa6bfeb9fa93b021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cef29f694bdf97adc4dc282c0398cbb2286f1eeb50dbe18275bd4d947a03e5a 0.600000000000 1532163 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": 1061678, "vin": [ { "gen": { "height": 1061668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cef29f694bdf97adc4dc282c0398cbb2286f1eeb50dbe18275bd4d947a03e5a" } } ], "extra": [ 1, 17, 244, 41, 17, 105, 134, 86, 116, 244, 222, 167, 177, 108, 41, 42, 89, 41, 179, 193, 178, 180, 55, 19, 139, 122, 202, 166, 191, 235, 159, 169, 59, 2, 17, 0, 0, 0, 3, 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