Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 722bacae08795603d61cc668c0cdecde7f3d6f953fff3b002d59e8e2aabc9277

Tx prefix hash: 679f24e3386ac7acf55b59ba47b747f95ef52acfc13b23aa778db24d1c42ab7a
Tx public key: 3f64eb74baee0d80666c5ff286a548bc1c37f4aa2c2afe809097acd9e022d272
Timestamp: 1751132983 Timestamp [UCT]: 2025-06-28 17:49:43 Age [y:d:h:m:s]: 00:140:08:38:27
Block: 1314680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98399 RingCT/type: yes/0
Extra: 013f64eb74baee0d80666c5ff286a548bc1c37f4aa2c2afe809097acd9e022d272021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b50f0a09830bf6701cbc9104247469fe38e9b0383336c8d5fdf489bbe0e45448 0.600000000000 1802331 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": 1314690, "vin": [ { "gen": { "height": 1314680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b50f0a09830bf6701cbc9104247469fe38e9b0383336c8d5fdf489bbe0e45448" } } ], "extra": [ 1, 63, 100, 235, 116, 186, 238, 13, 128, 102, 108, 95, 242, 134, 165, 72, 188, 28, 55, 244, 170, 44, 42, 254, 128, 144, 151, 172, 217, 224, 34, 210, 114, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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