Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8286d017eb4cf450c7dd2f702a92e98825c8fc823dc528d103f7d567b3f45462

Tx prefix hash: 0145749d18a3db4f7d5e01bde29f2c6aa3052dd01162bf49bfb143e96cce868f
Tx public key: 2c7af3b4354e23bf8ddd0caf69f224249d70abd629a7792afd02c23bf48405af
Timestamp: 1656968024 Timestamp [UCT]: 2022-07-04 20:53:44 Age [y:d:h:m:s]: 03:119:09:18:27
Block: 536686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 865055 RingCT/type: yes/0
Extra: 012c7af3b4354e23bf8ddd0caf69f224249d70abd629a7792afd02c23bf48405af0211000000035eb576c5000000000000000000

1 output(s) for total of 10.226726579000 dcy

stealth address amount amount idx
00: 2ead966ae5e1cca19cf5c3eae636e9aba813cb534dc9f574af90b9d860d3484f 10.226726579000 966475 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": 536696, "vin": [ { "gen": { "height": 536686 } } ], "vout": [ { "amount": 10226726579, "target": { "key": "2ead966ae5e1cca19cf5c3eae636e9aba813cb534dc9f574af90b9d860d3484f" } } ], "extra": [ 1, 44, 122, 243, 180, 53, 78, 35, 191, 141, 221, 12, 175, 105, 242, 36, 36, 157, 112, 171, 214, 41, 167, 121, 42, 253, 2, 194, 59, 244, 132, 5, 175, 2, 17, 0, 0, 0, 3, 94, 181, 118, 197, 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