Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2d7720283f9e41bac4a48fdcd491cbc122e6d4e26a69f7b35fc4fd428aee482

Tx prefix hash: 03a2795dc3b1449413a258616007810a26aff82dba911fbaf2b357f2ab57ad21
Tx public key: e8ffa7bea24341fa97c3ece258f5a14258cca9e1b9ad8e993154a8d2aacf946f
Timestamp: 1705890969 Timestamp [UCT]: 2024-01-22 02:36:09 Age [y:d:h:m:s]: 01:260:13:15:34
Block: 940545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444996 RingCT/type: yes/0
Extra: 01e8ffa7bea24341fa97c3ece258f5a14258cca9e1b9ad8e993154a8d2aacf946f0211000000217a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4de4825c7660782e2d948c693920146efff1150ba68b228b9a89ce36621b4900 0.600000000000 1398683 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": 940555, "vin": [ { "gen": { "height": 940545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4de4825c7660782e2d948c693920146efff1150ba68b228b9a89ce36621b4900" } } ], "extra": [ 1, 232, 255, 167, 190, 162, 67, 65, 250, 151, 195, 236, 226, 88, 245, 161, 66, 88, 204, 169, 225, 185, 173, 142, 153, 49, 84, 168, 210, 170, 207, 148, 111, 2, 17, 0, 0, 0, 33, 122, 156, 244, 199, 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