Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59d62175f365a9fcf71e9222022d724182178c4d75a207c3c9309fca5c2235e2

Tx prefix hash: 2aaf2a2902418e8a4ecb6f5f4925b4808c34c8474dd81e27a560855e4acdb80d
Tx public key: e898fe2629b6b92d18cdc5790df28e77dc3712d8ed3c76fa10f24e6f399c7e79
Timestamp: 1745436896 Timestamp [UCT]: 2025-04-23 19:34:56 Age [y:d:h:m:s]: 00:019:00:48:37
Block: 1267928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13609 RingCT/type: yes/0
Extra: 01e898fe2629b6b92d18cdc5790df28e77dc3712d8ed3c76fa10f24e6f399c7e79021100000013dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2385b97a78181ee6055c2c60416093a6b3e0a0fa89065fc7b392e156cf3ef0b2 0.600000000000 1755157 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": 1267938, "vin": [ { "gen": { "height": 1267928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2385b97a78181ee6055c2c60416093a6b3e0a0fa89065fc7b392e156cf3ef0b2" } } ], "extra": [ 1, 232, 152, 254, 38, 41, 182, 185, 45, 24, 205, 197, 121, 13, 242, 142, 119, 220, 55, 18, 216, 237, 60, 118, 250, 16, 242, 78, 111, 57, 156, 126, 121, 2, 17, 0, 0, 0, 19, 219, 181, 113, 193, 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