Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82e2825a4c50a523282bd419c2a968bfba14cb7607ca9f1e265235db0e5d442d

Tx prefix hash: cb39e45674537e82b28e6d6f6f64dd9506a6e3d14ab79b6128ec6ceef3461c1c
Tx public key: c50f2ab5bf22d33263ed3da353790c895054a36240f125a1861c58d39fb29322
Timestamp: 1705742141 Timestamp [UCT]: 2024-01-20 09:15:41 Age [y:d:h:m:s]: 01:136:12:37:17
Block: 939316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358732 RingCT/type: yes/0
Extra: 01c50f2ab5bf22d33263ed3da353790c895054a36240f125a1861c58d39fb293220211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7125a636f71b4f047c69c0f92276d24bcb47ce3e1fd5c919fae8f88af92eaee 0.600000000000 1397410 of 15

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": 939326, "vin": [ { "gen": { "height": 939316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7125a636f71b4f047c69c0f92276d24bcb47ce3e1fd5c919fae8f88af92eaee" } } ], "extra": [ 1, 197, 15, 42, 181, 191, 34, 211, 50, 99, 237, 61, 163, 83, 121, 12, 137, 80, 84, 163, 98, 64, 241, 37, 161, 134, 28, 88, 211, 159, 178, 147, 34, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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