Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5446b70f37a06f516c328ca23c879866635a0c6d99ea15e19ea436e66139650f

Tx prefix hash: d3ae610f7788da7889a5e59b359754a5942e01f334995126fe9356db5574b2a7
Tx public key: 4ad54133918729c179d0b651221c713aa67a93c88d00b323511798b71027c2ce
Timestamp: 1582026733 Timestamp [UCT]: 2020-02-18 11:52:13 Age [y:d:h:m:s]: 05:084:15:43:47
Block: 67341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1213698 RingCT/type: yes/0
Extra: 014ad54133918729c179d0b651221c713aa67a93c88d00b323511798b71027c2ce021100000002d81c26c0000000000000000000

1 output(s) for total of 367.174168460000 dcy

stealth address amount amount idx
00: b988b6e119c430094d13c6ff90bbf15f0041c3e54f9ace86c105dfb964a20c7e 367.174168460000 124125 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": 67351, "vin": [ { "gen": { "height": 67341 } } ], "vout": [ { "amount": 367174168460, "target": { "key": "b988b6e119c430094d13c6ff90bbf15f0041c3e54f9ace86c105dfb964a20c7e" } } ], "extra": [ 1, 74, 213, 65, 51, 145, 135, 41, 193, 121, 208, 182, 81, 34, 28, 113, 58, 166, 122, 147, 200, 141, 0, 179, 35, 81, 23, 152, 183, 16, 39, 194, 206, 2, 17, 0, 0, 0, 2, 216, 28, 38, 192, 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