Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 228c0e65ef80d07c9bfd23a7d3a79bbedf336c6d4540eaf0585bcf39ef65f58e

Tx prefix hash: 17c765086dd82618016445dc464050e19a8196571ea1375026cf6b96049c1d61
Tx public key: 5c89ca9f1c562a1c9ca174a9682f2ecae51b4f64064e50efc2f5ccf92d93020a
Timestamp: 1675425657 Timestamp [UCT]: 2023-02-03 12:00:57 Age [y:d:h:m:s]: 01:344:13:26:10
Block: 688890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507233 RingCT/type: yes/0
Extra: 015c89ca9f1c562a1c9ca174a9682f2ecae51b4f64064e50efc2f5ccf92d93020a0211000000015029cbac000000000000000000

1 output(s) for total of 3.202000443000 dcy

stealth address amount amount idx
00: aec6e07c2e1aa7fc8dbd534edf9a2fcf5091adfef682dd8b97f1d0943433d97a 3.202000443000 1131544 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": 688900, "vin": [ { "gen": { "height": 688890 } } ], "vout": [ { "amount": 3202000443, "target": { "key": "aec6e07c2e1aa7fc8dbd534edf9a2fcf5091adfef682dd8b97f1d0943433d97a" } } ], "extra": [ 1, 92, 137, 202, 159, 28, 86, 42, 28, 156, 161, 116, 169, 104, 47, 46, 202, 229, 27, 79, 100, 6, 78, 80, 239, 194, 245, 204, 249, 45, 147, 2, 10, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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