Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4db07958f2ccbdf47924b51ce07f0c9a2158b87f64cbd755add5fdd3595d8dbb

Tx prefix hash: e08e90efec7a3ba68189f943e744aadc970e6b330597e18e6d9aebf48cf569d8
Tx public key: f350b9f83e6b545231626dbeb4670803d2105e84b8727586d1caf9dc35410cc4
Timestamp: 1758423910 Timestamp [UCT]: 2025-09-21 03:05:10 Age [y:d:h:m:s]: 00:092:05:44:52
Block: 1372992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66045 RingCT/type: yes/0
Extra: 01f350b9f83e6b545231626dbeb4670803d2105e84b8727586d1caf9dc35410cc4021100000001b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1fd68930112d1da42959f7eca7320bc5b5751fd83bf5f671d8b9b58fb54f6a1 0.600000000000 1861077 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": 1373002, "vin": [ { "gen": { "height": 1372992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1fd68930112d1da42959f7eca7320bc5b5751fd83bf5f671d8b9b58fb54f6a1" } } ], "extra": [ 1, 243, 80, 185, 248, 62, 107, 84, 82, 49, 98, 109, 190, 180, 103, 8, 3, 210, 16, 94, 132, 184, 114, 117, 134, 209, 202, 249, 220, 53, 65, 12, 196, 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