Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6565d60c9114e323bd17cf201a09396b410dc28e31e3631ee0a9d7e3c3b1812

Tx prefix hash: 1ae65109463780c5c221c4aa217ae00640743ecc91655005b543fa9b43de6c6f
Tx public key: 4023a94e5bc4713582899e72d2a6775281285b8117f7b3c1c85d3198f26237c0
Timestamp: 1585415371 Timestamp [UCT]: 2020-03-28 17:09:31 Age [y:d:h:m:s]: 04:279:14:05:12
Block: 88803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1098908 RingCT/type: yes/0
Extra: 014023a94e5bc4713582899e72d2a6775281285b8117f7b3c1c85d3198f26237c002110000003ba86a1a65000000000000000000

1 output(s) for total of 311.716344176000 dcy

stealth address amount amount idx
00: 9b1a9891ca6ac10108ac2478ef95f3405ba34cd9dfde0e636bf28de1d36d6919 311.716344176000 159573 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": 88813, "vin": [ { "gen": { "height": 88803 } } ], "vout": [ { "amount": 311716344176, "target": { "key": "9b1a9891ca6ac10108ac2478ef95f3405ba34cd9dfde0e636bf28de1d36d6919" } } ], "extra": [ 1, 64, 35, 169, 78, 91, 196, 113, 53, 130, 137, 158, 114, 210, 166, 119, 82, 129, 40, 91, 129, 23, 247, 179, 193, 200, 93, 49, 152, 242, 98, 55, 192, 2, 17, 0, 0, 0, 59, 168, 106, 26, 101, 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