Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 073b3a8da4a98965051192a8ffcc0a1b84fae853bfb736eb32c097dcba9bea6c

Tx prefix hash: 9b6841e20a3ff061d74de2f1788a1583a3b81444468d02fad0f0c12481860231
Tx public key: 107261aa3ff4135ef149e3f8547a52a79d74a21e321e4408e8ecb7b9d4fd8b75
Timestamp: 1577552543 Timestamp [UCT]: 2019-12-28 17:02:23 Age [y:d:h:m:s]: 05:101:23:56:25
Block: 33631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1222758 RingCT/type: yes/0
Extra: 01107261aa3ff4135ef149e3f8547a52a79d74a21e321e4408e8ecb7b9d4fd8b75021100000025feadaf7f000000000000000000

1 output(s) for total of 474.872783491000 dcy

stealth address amount amount idx
00: f849cc422365804cb826ca9d9bf7c41b5caa4ed97eb7b37a8f71b95c6f9dc861 474.872783491000 56387 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": 33641, "vin": [ { "gen": { "height": 33631 } } ], "vout": [ { "amount": 474872783491, "target": { "key": "f849cc422365804cb826ca9d9bf7c41b5caa4ed97eb7b37a8f71b95c6f9dc861" } } ], "extra": [ 1, 16, 114, 97, 170, 63, 244, 19, 94, 241, 73, 227, 248, 84, 122, 82, 167, 157, 116, 162, 30, 50, 30, 68, 8, 232, 236, 183, 185, 212, 253, 139, 117, 2, 17, 0, 0, 0, 37, 254, 173, 175, 127, 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