Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49d2e0e0c982601f4ce742dc1e3db066f773be97b3259b9f9febbfc93d846864

Tx prefix hash: 9168d1ae7b45276d710dce65cb781028501bf370231f67b6dcbe010ed17e41e6
Tx public key: b925b6e67f95a80718a1b03d9b6bf5ec013946fee2ab00e6bf137b0450750627
Timestamp: 1638394516 Timestamp [UCT]: 2021-12-01 21:35:16 Age [y:d:h:m:s]: 03:103:18:23:44
Block: 386359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 852871 RingCT/type: yes/0
Extra: 01b925b6e67f95a80718a1b03d9b6bf5ec013946fee2ab00e6bf137b0450750627021100000001f6cc1430000000000000000000

1 output(s) for total of 32.198276028000 dcy

stealth address amount amount idx
00: d4bd15058121a7c8a52d6a51f9ccdf80f0c40bdf0a9f70254d5c782db1b0ab4b 32.198276028000 779492 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": 386369, "vin": [ { "gen": { "height": 386359 } } ], "vout": [ { "amount": 32198276028, "target": { "key": "d4bd15058121a7c8a52d6a51f9ccdf80f0c40bdf0a9f70254d5c782db1b0ab4b" } } ], "extra": [ 1, 185, 37, 182, 230, 127, 149, 168, 7, 24, 161, 176, 61, 155, 107, 245, 236, 1, 57, 70, 254, 226, 171, 0, 230, 191, 19, 123, 4, 80, 117, 6, 39, 2, 17, 0, 0, 0, 1, 246, 204, 20, 48, 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