Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0321457cbfa22ec6cd35eeb6049e2ad1d8582c526fe36a42c93841ae42d7078e

Tx prefix hash: c3de29036e24fb0ea936f12ba1cd78b48f1bac4e93cff247681b80d924aecf5d
Tx public key: b9c8ec6624294513fa91c17304bab22fd3115a7872059d2ad8a0b014726d9230
Timestamp: 1737040928 Timestamp [UCT]: 2025-01-16 15:22:08 Age [y:d:h:m:s]: 00:061:01:22:49
Block: 1198682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43424 RingCT/type: yes/0
Extra: 01b9c8ec6624294513fa91c17304bab22fd3115a7872059d2ad8a0b014726d9230021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5f2258a67339f6a48458ee3c6a4045d369fd2a3881c94a2588a3373d91ecccb 0.600000000000 1685307 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": 1198692, "vin": [ { "gen": { "height": 1198682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5f2258a67339f6a48458ee3c6a4045d369fd2a3881c94a2588a3373d91ecccb" } } ], "extra": [ 1, 185, 200, 236, 102, 36, 41, 69, 19, 250, 145, 193, 115, 4, 186, 178, 47, 211, 17, 90, 120, 114, 5, 157, 42, 216, 160, 176, 20, 114, 109, 146, 48, 2, 17, 0, 0, 0, 6, 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