Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c2224f720c9eca7772077a25858ff0eaf99d374941329daf4bec470b36e835e

Tx prefix hash: 514b9f5e3fc784c81d0ccc8006e234157c94400d32c472fc4c9f1952b0ec7484
Tx public key: eab5ebc856c95460626d6a8ef3e39fd2e1d404335743e8dcc71c5e595cc1bb1d
Timestamp: 1645302905 Timestamp [UCT]: 2022-02-19 20:35:05 Age [y:d:h:m:s]: 02:354:13:48:01
Block: 442143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 772588 RingCT/type: yes/0
Extra: 01eab5ebc856c95460626d6a8ef3e39fd2e1d404335743e8dcc71c5e595cc1bb1d0211000000024a0f5013000000000000000000

1 output(s) for total of 21.037638541000 dcy

stealth address amount amount idx
00: 35e5fccb7e181fd4bf1d1d6c5d5af0a92f68634e8685b8c5052369d9ece8b9f7 21.037638541000 854860 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": 442153, "vin": [ { "gen": { "height": 442143 } } ], "vout": [ { "amount": 21037638541, "target": { "key": "35e5fccb7e181fd4bf1d1d6c5d5af0a92f68634e8685b8c5052369d9ece8b9f7" } } ], "extra": [ 1, 234, 181, 235, 200, 86, 201, 84, 96, 98, 109, 106, 142, 243, 227, 159, 210, 225, 212, 4, 51, 87, 67, 232, 220, 199, 28, 94, 89, 92, 193, 187, 29, 2, 17, 0, 0, 0, 2, 74, 15, 80, 19, 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