Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c14dc940b7052772f17c96182ae46972472fb5e4fda3c335d961805c8dfc54f2

Tx prefix hash: 341ca2c198b65f8977bf910ae137400f130049bfd15edaebde1a35c968aaf965
Tx public key: 3de28e5278e75714f301be22c9b9acb65f2f83fdc8b54b2534edfa382c2e90e2
Timestamp: 1737497178 Timestamp [UCT]: 2025-01-21 22:06:18 Age [y:d:h:m:s]: 00:335:03:54:59
Block: 1202413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237143 RingCT/type: yes/0
Extra: 013de28e5278e75714f301be22c9b9acb65f2f83fdc8b54b2534edfa382c2e90e20211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac47924955baf3e0cd234f6a59cb1a222edba5ab78b0563c36985ca9bc9d963c 0.600000000000 1689076 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": 1202423, "vin": [ { "gen": { "height": 1202413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac47924955baf3e0cd234f6a59cb1a222edba5ab78b0563c36985ca9bc9d963c" } } ], "extra": [ 1, 61, 226, 142, 82, 120, 231, 87, 20, 243, 1, 190, 34, 201, 185, 172, 182, 95, 47, 131, 253, 200, 181, 75, 37, 52, 237, 250, 56, 44, 46, 144, 226, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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