Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a97b87c6aaf125e0e9074892cb94bf24dbb03956cae49901a5a3d95312a839a8

Tx prefix hash: dff40a65bc71993d65f4318008b39fe40c309975e02d316d58785b1cd9f96a3a
Tx public key: a7ed97bc20e13afc67adcf4cf790e9e9010d89b09338a861d7e3fcc4e304e8f9
Timestamp: 1617532881 Timestamp [UCT]: 2021-04-04 10:41:21 Age [y:d:h:m:s]: 03:304:08:08:02
Block: 233023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 976940 RingCT/type: yes/0
Extra: 01a7ed97bc20e13afc67adcf4cf790e9e9010d89b09338a861d7e3fcc4e304e8f90211000000023634f08d000000000000000000

1 output(s) for total of 103.738010896000 dcy

stealth address amount amount idx
00: f1c08414a61f0a01f027a8cdcf4bb54f3a2fe8e5d3094857c71b3145e2981b42 103.738010896000 484013 of 0

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": 233033, "vin": [ { "gen": { "height": 233023 } } ], "vout": [ { "amount": 103738010896, "target": { "key": "f1c08414a61f0a01f027a8cdcf4bb54f3a2fe8e5d3094857c71b3145e2981b42" } } ], "extra": [ 1, 167, 237, 151, 188, 32, 225, 58, 252, 103, 173, 207, 76, 247, 144, 233, 233, 1, 13, 137, 176, 147, 56, 168, 97, 215, 227, 252, 196, 227, 4, 232, 249, 2, 17, 0, 0, 0, 2, 54, 52, 240, 141, 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