Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86553b5d5b9ddde28ad6fae10947689f5ffa52ad763abe65ada46cb9a68a51b8

Tx prefix hash: 0fcf380db6c4a12e23ec1703c2b4ff78b9d134bf7a175ddb8669047f9fdc93ee
Tx public key: c0b65b0f352464f2a67e1b3797551ce6ebf5561c74d9f8640e8ddd6e23f59ef6
Timestamp: 1577638197 Timestamp [UCT]: 2019-12-29 16:49:57 Age [y:d:h:m:s]: 05:157:22:14:50
Block: 34425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1262709 RingCT/type: yes/0
Extra: 01c0b65b0f352464f2a67e1b3797551ce6ebf5561c74d9f8640e8ddd6e23f59ef60211000000164943cd9f000000000000000000

1 output(s) for total of 471.994067815000 dcy

stealth address amount amount idx
00: 83b9f41c0b0b70c6ed9cf7df0e268bba2960f3db8d144c4ac441a422c793054c 471.994067815000 57945 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": 34435, "vin": [ { "gen": { "height": 34425 } } ], "vout": [ { "amount": 471994067815, "target": { "key": "83b9f41c0b0b70c6ed9cf7df0e268bba2960f3db8d144c4ac441a422c793054c" } } ], "extra": [ 1, 192, 182, 91, 15, 53, 36, 100, 242, 166, 126, 27, 55, 151, 85, 28, 230, 235, 245, 86, 28, 116, 217, 248, 100, 14, 141, 221, 110, 35, 245, 158, 246, 2, 17, 0, 0, 0, 22, 73, 67, 205, 159, 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