Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5887ba5ea5af3098f6a6dc1bb95e7e3df1040c8b0e6b9b0694120e832e52830

Tx prefix hash: 8103258fa427ad75ee9e6c5afa9669fdc53867102d32b36c1ea06fb580e29d67
Tx public key: 1b1cdd275013573d8ce51a6190ad47cd14986de581381c67b6841e852fdb8826
Timestamp: 1583021578 Timestamp [UCT]: 2020-03-01 00:12:58 Age [y:d:h:m:s]: 04:312:04:06:22
Block: 74397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1116816 RingCT/type: yes/0
Extra: 011b1cdd275013573d8ce51a6190ad47cd14986de581381c67b6841e852fdb882602110000004803d36d11000000000000000000

1 output(s) for total of 347.936622019000 dcy

stealth address amount amount idx
00: 8217a614c2f74330d2aa14576bac3b6a6131e16b11caaa188860cc6db0c22af0 347.936622019000 137680 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": 74407, "vin": [ { "gen": { "height": 74397 } } ], "vout": [ { "amount": 347936622019, "target": { "key": "8217a614c2f74330d2aa14576bac3b6a6131e16b11caaa188860cc6db0c22af0" } } ], "extra": [ 1, 27, 28, 221, 39, 80, 19, 87, 61, 140, 229, 26, 97, 144, 173, 71, 205, 20, 152, 109, 229, 129, 56, 28, 103, 182, 132, 30, 133, 47, 219, 136, 38, 2, 17, 0, 0, 0, 72, 3, 211, 109, 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