Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0949527793a8ae20ab852c405c85ecb7f0a3945976c9de46821878f5ddd0761f

Tx prefix hash: bb8086e13d46cd523259c276c3d4c874143c3aa694f4af385bc56a3b78596b59
Tx public key: a7fc97012dc12b1814adc15be801e174ac01b69565dfb9d756d8c3fa767be593
Timestamp: 1700891797 Timestamp [UCT]: 2023-11-25 05:56:37 Age [y:d:h:m:s]: 01:001:07:35:17
Block: 899135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262301 RingCT/type: yes/0
Extra: 01a7fc97012dc12b1814adc15be801e174ac01b69565dfb9d756d8c3fa767be593021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.643861535000 dcy

stealth address amount amount idx
00: a715435a14d703c32170ef79d4312f3921d25c8c6d828ca1f915346647252003 0.643861535000 1355578 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": 899145, "vin": [ { "gen": { "height": 899135 } } ], "vout": [ { "amount": 643861535, "target": { "key": "a715435a14d703c32170ef79d4312f3921d25c8c6d828ca1f915346647252003" } } ], "extra": [ 1, 167, 252, 151, 1, 45, 193, 43, 24, 20, 173, 193, 91, 232, 1, 225, 116, 172, 1, 182, 149, 101, 223, 185, 215, 86, 216, 195, 250, 118, 123, 229, 147, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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