Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3685ca26370524d9936c9d4d9a6956a10e2bce5c1f89ed83bde6b01985d6357

Tx prefix hash: 54dbc4b295df16addd66827a6c764f560f0c4de5dc4d90582acfde0f52bcac9f
Tx public key: f850023af6a68fe26bd2899d7b77e534baf00e7a208509e746caca8f9ec897e0
Timestamp: 1737630537 Timestamp [UCT]: 2025-01-23 11:08:57 Age [y:d:h:m:s]: 00:148:04:43:08
Block: 1203527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105620 RingCT/type: yes/0
Extra: 01f850023af6a68fe26bd2899d7b77e534baf00e7a208509e746caca8f9ec897e00211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8669082b69bf82faeb0fff3e1a63797a8afef9ba7ed5880d3db36d8227f0ee75 0.600000000000 1690204 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": 1203537, "vin": [ { "gen": { "height": 1203527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8669082b69bf82faeb0fff3e1a63797a8afef9ba7ed5880d3db36d8227f0ee75" } } ], "extra": [ 1, 248, 80, 2, 58, 246, 166, 143, 226, 107, 210, 137, 157, 123, 119, 229, 52, 186, 240, 14, 122, 32, 133, 9, 231, 70, 202, 202, 143, 158, 200, 151, 224, 2, 17, 0, 0, 0, 3, 131, 104, 38, 109, 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