Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd2af9918b53b687d783df879640f77e6d916279a52c19d020f75fa8a64d3245

Tx prefix hash: 2ef6b4f2b41d3c10bac3842258109b12fbbc61cba2426ae73e22a004e85d4ac2
Tx public key: 36a231a382a3196fc5749fdcdf4b2714ecab9bbdf886713c35c0cbfe981e127e
Timestamp: 1752810055 Timestamp [UCT]: 2025-07-18 03:40:55 Age [y:d:h:m:s]: 00:082:15:25:52
Block: 1327851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57793 RingCT/type: yes/0
Extra: 0136a231a382a3196fc5749fdcdf4b2714ecab9bbdf886713c35c0cbfe981e127e021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30f26f2bd6b9365bfec235e27e281b641a8e2f15d60d5b1f1338b168c30e4ff0 0.600000000000 1815610 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": 1327861, "vin": [ { "gen": { "height": 1327851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30f26f2bd6b9365bfec235e27e281b641a8e2f15d60d5b1f1338b168c30e4ff0" } } ], "extra": [ 1, 54, 162, 49, 163, 130, 163, 25, 111, 197, 116, 159, 220, 223, 75, 39, 20, 236, 171, 155, 189, 248, 134, 113, 60, 53, 192, 203, 254, 152, 30, 18, 126, 2, 17, 0, 0, 0, 3, 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