Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac55208bdfdb7dc3d22ee9d390bc16a86e8d9e94d7f67f197e467898cf27b484

Tx prefix hash: a5d69c852b427cf8aea8b2c2ff781355f15dee1f89f3476747d4bc97e333755f
Tx public key: 925a9d37afe53b82d2e5a5aba82ba82f3285dc58a3155929e18309e8a6fe34ee
Timestamp: 1737656215 Timestamp [UCT]: 2025-01-23 18:16:55 Age [y:d:h:m:s]: 00:297:04:29:00
Block: 1203734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209943 RingCT/type: yes/0
Extra: 01925a9d37afe53b82d2e5a5aba82ba82f3285dc58a3155929e18309e8a6fe34ee0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5202c7642bf0c4368efafad8c6abd2e1c77af1b85ee69e65ae50b431ec16dbb 0.600000000000 1690413 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": 1203744, "vin": [ { "gen": { "height": 1203734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5202c7642bf0c4368efafad8c6abd2e1c77af1b85ee69e65ae50b431ec16dbb" } } ], "extra": [ 1, 146, 90, 157, 55, 175, 229, 59, 130, 210, 229, 165, 171, 168, 43, 168, 47, 50, 133, 220, 88, 163, 21, 89, 41, 225, 131, 9, 232, 166, 254, 52, 238, 2, 17, 0, 0, 0, 3, 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