Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 526f50920d22dcd11006f081224cf3b6651d2bb8401e1b9d188e2de1da25981d

Tx prefix hash: d1816ccffd3cc81b0ed15d5fc066f02352c2c9163b89861d8713bd52366a44aa
Tx public key: 84b8adbe4e6e4678c92dd051a2e5f22c1c93268e1347e6ee70fec1500a980735
Timestamp: 1756993567 Timestamp [UCT]: 2025-09-04 13:46:07 Age [y:d:h:m:s]: 00:147:19:18:18
Block: 1361223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105581 RingCT/type: yes/0
Extra: 0184b8adbe4e6e4678c92dd051a2e5f22c1c93268e1347e6ee70fec1500a980735021100000001b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c816b5133723ea14c336419deecb58c0c1fb303e6100919ab64c33d083c13e2 0.600000000000 1849236 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": 1361233, "vin": [ { "gen": { "height": 1361223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c816b5133723ea14c336419deecb58c0c1fb303e6100919ab64c33d083c13e2" } } ], "extra": [ 1, 132, 184, 173, 190, 78, 110, 70, 120, 201, 45, 208, 81, 162, 229, 242, 44, 28, 147, 38, 142, 19, 71, 230, 238, 112, 254, 193, 80, 10, 152, 7, 53, 2, 17, 0, 0, 0, 1, 178, 247, 132, 196, 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