Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afbf42eb807c8574aaa9acc8526d032036b60faa94231d62ba23edb708f69b6d

Tx prefix hash: 0dadd0e7b6fd06bda36a601bc2c1c57e31c358fce64e23be2b5968eae4f62ad3
Tx public key: 9cddbf9544a4bdb9f01834f248ebadfeacc48fd97a9a675718abbda22cd935f1
Timestamp: 1577786141 Timestamp [UCT]: 2019-12-31 09:55:41 Age [y:d:h:m:s]: 05:154:01:45:51
Block: 35607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1259998 RingCT/type: yes/0
Extra: 019cddbf9544a4bdb9f01834f248ebadfeacc48fd97a9a675718abbda22cd935f1021100000005d81c26c0000000000000000000

1 output(s) for total of 467.756769994000 dcy

stealth address amount amount idx
00: a080d9cbd327ac2761044e283c8f8e435974f6452dca6c14d64aba8a68da475e 467.756769994000 60106 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": 35617, "vin": [ { "gen": { "height": 35607 } } ], "vout": [ { "amount": 467756769994, "target": { "key": "a080d9cbd327ac2761044e283c8f8e435974f6452dca6c14d64aba8a68da475e" } } ], "extra": [ 1, 156, 221, 191, 149, 68, 164, 189, 185, 240, 24, 52, 242, 72, 235, 173, 254, 172, 196, 143, 217, 122, 154, 103, 87, 24, 171, 189, 162, 44, 217, 53, 241, 2, 17, 0, 0, 0, 5, 216, 28, 38, 192, 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