Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8c805225972e99d60a807ae6eed15045e2923ac905e81038a3c8a7c6c0d434a

Tx prefix hash: 555987a3c7e346e0d4bab15ae1e3276cd964eaac01c54825e9ce85092006153e
Tx public key: 2067dbb5cc248de027d17cda6257e6f436fe6e018772792e44adce8f5329a1d7
Timestamp: 1581935440 Timestamp [UCT]: 2020-02-17 10:30:40 Age [y:d:h:m:s]: 05:016:21:29:32
Block: 66570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1165249 RingCT/type: yes/0
Extra: 012067dbb5cc248de027d17cda6257e6f436fe6e018772792e44adce8f5329a1d70211000000078a2ee0d9000000000000000000

1 output(s) for total of 369.340356614000 dcy

stealth address amount amount idx
00: e9485b87e4cf94afe92451329f98437e2e9431e3d1c5fae88fc0935cbea7fe49 369.340356614000 122653 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": 66580, "vin": [ { "gen": { "height": 66570 } } ], "vout": [ { "amount": 369340356614, "target": { "key": "e9485b87e4cf94afe92451329f98437e2e9431e3d1c5fae88fc0935cbea7fe49" } } ], "extra": [ 1, 32, 103, 219, 181, 204, 36, 141, 224, 39, 209, 124, 218, 98, 87, 230, 244, 54, 254, 110, 1, 135, 114, 121, 46, 68, 173, 206, 143, 83, 41, 161, 215, 2, 17, 0, 0, 0, 7, 138, 46, 224, 217, 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