Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6650347f55b29bd81078ab02d8754bdbd81268d1c27d1a6a9fcd0d60f279a44f

Tx prefix hash: eb86c3dfa93a778c7356b8eb3ed340e50485d82e208ad4bb3a09e37e2d395555
Tx public key: a11e995828b8f091a2f2c45a27211456af24a3fef737e3c438935e92bb266fcc
Timestamp: 1582505148 Timestamp [UCT]: 2020-02-24 00:45:48 Age [y:d:h:m:s]: 05:045:23:58:28
Block: 70989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1186359 RingCT/type: yes/0
Extra: 01a11e995828b8f091a2f2c45a27211456af24a3fef737e3c438935e92bb266fcc021100000001c71d3ff9000000000000000000

1 output(s) for total of 357.101987996000 dcy

stealth address amount amount idx
00: 6815bb3365fdbc38341a638eda61ca8d3f09778ab7b0a06c43be93962cf04fe2 357.101987996000 131246 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": 70999, "vin": [ { "gen": { "height": 70989 } } ], "vout": [ { "amount": 357101987996, "target": { "key": "6815bb3365fdbc38341a638eda61ca8d3f09778ab7b0a06c43be93962cf04fe2" } } ], "extra": [ 1, 161, 30, 153, 88, 40, 184, 240, 145, 162, 242, 196, 90, 39, 33, 20, 86, 175, 36, 163, 254, 247, 55, 227, 196, 56, 147, 94, 146, 187, 38, 111, 204, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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