Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee1313518b01882283cda1c066ca47306c2f54d4739885b9a4f13d88fb0918c9

Tx prefix hash: e49acc5a9d83197c32b614071412f55d6e073f201db188456ad678bdb0fb336c
Tx public key: ba7a995a1dc2f849329ad05626d863aa551c70fcf0efc4a41d72babdbefeaf23
Timestamp: 1699545838 Timestamp [UCT]: 2023-11-09 16:03:58 Age [y:d:h:m:s]: 00:349:12:24:07
Block: 887987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250321 RingCT/type: yes/0
Extra: 01ba7a995a1dc2f849329ad05626d863aa551c70fcf0efc4a41d72babdbefeaf23021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.701090065000 dcy

stealth address amount amount idx
00: fe19a54eb143ec0d536b724d043586fe8f149209e11697dc2e53209c864950b9 0.701090065000 1343902 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": 887997, "vin": [ { "gen": { "height": 887987 } } ], "vout": [ { "amount": 701090065, "target": { "key": "fe19a54eb143ec0d536b724d043586fe8f149209e11697dc2e53209c864950b9" } } ], "extra": [ 1, 186, 122, 153, 90, 29, 194, 248, 73, 50, 154, 208, 86, 38, 216, 99, 170, 85, 28, 112, 252, 240, 239, 196, 164, 29, 114, 186, 189, 190, 254, 175, 35, 2, 17, 0, 0, 0, 4, 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