Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1e53bd5bae035ce07b9651c079286d5a3a3cc8692cc6fe35165f3e8adeeea51

Tx prefix hash: 864073dba46c123b539ab4549fa0da4261f4f920eb05e303b3ce692d27e94c18
Tx public key: e2ad77423e135879f4a5167c29c30e8230fcb9fa8ecb4472fc68364058e0b2f8
Timestamp: 1635089708 Timestamp [UCT]: 2021-10-24 15:35:08 Age [y:d:h:m:s]: 03:141:18:10:17
Block: 359573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 879468 RingCT/type: yes/0
Extra: 01e2ad77423e135879f4a5167c29c30e8230fcb9fa8ecb4472fc68364058e0b2f802110000000cf29d7abf000000000000000000

1 output(s) for total of 39.498972171000 dcy

stealth address amount amount idx
00: c2315d6f2988643e022d0a5999e65389d9128170c82a309da9c35b9688b402b8 39.498972171000 732162 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": 359583, "vin": [ { "gen": { "height": 359573 } } ], "vout": [ { "amount": 39498972171, "target": { "key": "c2315d6f2988643e022d0a5999e65389d9128170c82a309da9c35b9688b402b8" } } ], "extra": [ 1, 226, 173, 119, 66, 62, 19, 88, 121, 244, 165, 22, 124, 41, 195, 14, 130, 48, 252, 185, 250, 142, 203, 68, 114, 252, 104, 54, 64, 88, 224, 178, 248, 2, 17, 0, 0, 0, 12, 242, 157, 122, 191, 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