Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c236ca8389b4a8b60d93277c340e1d2f2aada400bc2f8457e282fe2e73adf6f8

Tx prefix hash: 227c70bd90a2139e3a49eb5a6c3157ad293f174fd3f21b948bb3409944e0ebde
Tx public key: e9fc8a0729f0c3e70d13a8e7898572545c1df26572261010ceaafa87146a418e
Timestamp: 1578824779 Timestamp [UCT]: 2020-01-12 10:26:19 Age [y:d:h:m:s]: 04:352:16:13:02
Block: 43875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1141561 RingCT/type: yes/0
Extra: 01e9fc8a0729f0c3e70d13a8e7898572545c1df26572261010ceaafa87146a418e02110000003adcee4b4d000000000000000000

1 output(s) for total of 439.161999323000 dcy

stealth address amount amount idx
00: 32975ca9540d90af473835a16e31b71706f608b3f89bfaef2f342e6aa1ea259a 439.161999323000 79620 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": 43885, "vin": [ { "gen": { "height": 43875 } } ], "vout": [ { "amount": 439161999323, "target": { "key": "32975ca9540d90af473835a16e31b71706f608b3f89bfaef2f342e6aa1ea259a" } } ], "extra": [ 1, 233, 252, 138, 7, 41, 240, 195, 231, 13, 19, 168, 231, 137, 133, 114, 84, 92, 29, 242, 101, 114, 38, 16, 16, 206, 170, 250, 135, 20, 106, 65, 142, 2, 17, 0, 0, 0, 58, 220, 238, 75, 77, 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