Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b46ff3eb656890c482a1c616eca5f67c8942bf4f373f9bf82a672a29a9d41709

Tx prefix hash: bb8514fd17900a5571056b946bba10bc25d029da5bca3ba991ff5d8aa5eb76c7
Tx public key: 0ba3fd46669b75bd79a28719db0a7ed8a05945c5b36a31bfdd7ef4a9efdf3be8
Timestamp: 1745341185 Timestamp [UCT]: 2025-04-22 16:59:45 Age [y:d:h:m:s]: 00:014:03:09:22
Block: 1267135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10111 RingCT/type: yes/0
Extra: 010ba3fd46669b75bd79a28719db0a7ed8a05945c5b36a31bfdd7ef4a9efdf3be80211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02d9994422ffa6bd80aabb434f9821e70491b48936458e732eb7a6775e80532c 0.600000000000 1754362 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": 1267145, "vin": [ { "gen": { "height": 1267135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02d9994422ffa6bd80aabb434f9821e70491b48936458e732eb7a6775e80532c" } } ], "extra": [ 1, 11, 163, 253, 70, 102, 155, 117, 189, 121, 162, 135, 25, 219, 10, 126, 216, 160, 89, 69, 197, 179, 106, 49, 191, 221, 126, 244, 169, 239, 223, 59, 232, 2, 17, 0, 0, 0, 5, 108, 152, 170, 61, 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