Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 842d53aa717624fe8313992d0b2247a8fabd279ba7353a283375e055528ae73d

Tx prefix hash: 61110c58918652aec7852b9f197bad7fc1a9705306541f31cf5042964c34d9da
Tx public key: cebacc2638cdf375e5bb28e6c4659b7731f3fcb1471d6cbc8dcb03686d9d10c9
Timestamp: 1633968777 Timestamp [UCT]: 2021-10-11 16:12:57 Age [y:d:h:m:s]: 04:020:22:56:42
Block: 351177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1050826 RingCT/type: yes/0
Extra: 01cebacc2638cdf375e5bb28e6c4659b7731f3fcb1471d6cbc8dcb03686d9d10c90211000000115d7cc334000000000000000000

1 output(s) for total of 42.111939116000 dcy

stealth address amount amount idx
00: edde2491c6b78f7af34e6d61f84604d4c2fb6fd35d6bb12af6f2429893db033d 42.111939116000 718291 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": 351187, "vin": [ { "gen": { "height": 351177 } } ], "vout": [ { "amount": 42111939116, "target": { "key": "edde2491c6b78f7af34e6d61f84604d4c2fb6fd35d6bb12af6f2429893db033d" } } ], "extra": [ 1, 206, 186, 204, 38, 56, 205, 243, 117, 229, 187, 40, 230, 196, 101, 155, 119, 49, 243, 252, 177, 71, 29, 108, 188, 141, 203, 3, 104, 109, 157, 16, 201, 2, 17, 0, 0, 0, 17, 93, 124, 195, 52, 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