Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb21154529f62c7ec0b3564915a5eebb109fe1fb4338b3227839d92f154bf9a1

Tx prefix hash: 1b67725ccfb2726532c75a8a907029b4b3f541afff5cd76113d7b9e4d19f7484
Tx public key: d1103915c8eb6e27ee0f4327267b9bd697ed5d2676dc8371d4b12ece66393a3f
Timestamp: 1720556520 Timestamp [UCT]: 2024-07-09 20:22:00 Age [y:d:h:m:s]: 01:122:22:01:21
Block: 1062175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346370 RingCT/type: yes/0
Extra: 01d1103915c8eb6e27ee0f4327267b9bd697ed5d2676dc8371d4b12ece66393a3f02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe1dc89c53a7811dfb0f22fbc7a7745fcb47f5e5dce22139b5e3a74cfb82d743 0.600000000000 1532676 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": 1062185, "vin": [ { "gen": { "height": 1062175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe1dc89c53a7811dfb0f22fbc7a7745fcb47f5e5dce22139b5e3a74cfb82d743" } } ], "extra": [ 1, 209, 16, 57, 21, 200, 235, 110, 39, 238, 15, 67, 39, 38, 123, 155, 214, 151, 237, 93, 38, 118, 220, 131, 113, 212, 177, 46, 206, 102, 57, 58, 63, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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