Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8760fd4e6453d5b8741c9a54b5926513cf5743dabb2063c95416fff52f82891a

Tx prefix hash: d5ad21e56492470e8af59a113ee330c6fa9459caa6e0c5d46cda99807b17391b
Tx public key: 9907d9c2807b35f027b6ef0ae44450b12338136cfb0fd4fe5e9710d4e022c7ec
Timestamp: 1703959104 Timestamp [UCT]: 2023-12-30 17:58:24 Age [y:d:h:m:s]: 01:167:18:32:03
Block: 924558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380971 RingCT/type: yes/0
Extra: 019907d9c2807b35f027b6ef0ae44450b12338136cfb0fd4fe5e9710d4e022c7ec021100000003ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4a1d668a567def6f4ad70cccc5999b3c44c902a914d9849f865b29a0de559eb 0.600000000000 1382312 of 15

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": 924568, "vin": [ { "gen": { "height": 924558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4a1d668a567def6f4ad70cccc5999b3c44c902a914d9849f865b29a0de559eb" } } ], "extra": [ 1, 153, 7, 217, 194, 128, 123, 53, 240, 39, 182, 239, 10, 228, 68, 80, 177, 35, 56, 19, 108, 251, 15, 212, 254, 94, 151, 16, 212, 224, 34, 199, 236, 2, 17, 0, 0, 0, 3, 172, 50, 141, 17, 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