Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11bcc4bab6ae4a0d8bdb327fed5a3b39f440ff695b6793d1890ac9f247014b08

Tx prefix hash: 0c83e54bf56e94aa52b6a762e730e3eb4e6a43319a24d5cef1344c4df0c0d563
Tx public key: 5ecb48325aa5a7e99086cbde0a4e5cf0d682cb6c779c661f7dcb0ae739ae8bf9
Timestamp: 1750817200 Timestamp [UCT]: 2025-06-25 02:06:40 Age [y:d:h:m:s]: 00:149:12:30:20
Block: 1312215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104793 RingCT/type: yes/0
Extra: 015ecb48325aa5a7e99086cbde0a4e5cf0d682cb6c779c661f7dcb0ae739ae8bf9021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f12000285f609dabcff6db908e65f8bf1d68389a979ab136ced60768d336f97e 0.600000000000 1799846 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": 1312225, "vin": [ { "gen": { "height": 1312215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f12000285f609dabcff6db908e65f8bf1d68389a979ab136ced60768d336f97e" } } ], "extra": [ 1, 94, 203, 72, 50, 90, 165, 167, 233, 144, 134, 203, 222, 10, 78, 92, 240, 214, 130, 203, 108, 119, 156, 102, 31, 125, 203, 10, 231, 57, 174, 139, 249, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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