Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afefa85f9634c42b892ee3272234ef51c56418ef5f2cc353b26c91f532b0bca4

Tx prefix hash: a95d0c030eaaa402e062d674544e364fbeab7e64bb16096f1d06a45eb5af88a8
Tx public key: 6c222c972ea511a6fe1db7b309af32ccdea2fdf088e34bc731bdceeb76a4d960
Timestamp: 1625036159 Timestamp [UCT]: 2021-06-30 06:55:59 Age [y:d:h:m:s]: 03:098:01:30:29
Block: 285744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 839099 RingCT/type: yes/0
Extra: 016c222c972ea511a6fe1db7b309af32ccdea2fdf088e34bc731bdceeb76a4d9600211000001be3525d189000000000000000000

1 output(s) for total of 69.376441682000 dcy

stealth address amount amount idx
00: 9b0ae0b3e315240398d52f3e603ba62c34f4cf2630807ea9ddc86ab88d5bf81c 69.376441682000 598355 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": 285754, "vin": [ { "gen": { "height": 285744 } } ], "vout": [ { "amount": 69376441682, "target": { "key": "9b0ae0b3e315240398d52f3e603ba62c34f4cf2630807ea9ddc86ab88d5bf81c" } } ], "extra": [ 1, 108, 34, 44, 151, 46, 165, 17, 166, 254, 29, 183, 179, 9, 175, 50, 204, 222, 162, 253, 240, 136, 227, 75, 199, 49, 189, 206, 235, 118, 164, 217, 96, 2, 17, 0, 0, 1, 190, 53, 37, 209, 137, 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