Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3220d3b2fca310555bb97eab607b5e944bad7f4e80b5e5afb735a1f803d70ab

Tx prefix hash: 6b1e830ac790bc76a8ecf307b82452e5658f93eb953c51060e9ec99ff2032baa
Tx public key: a2173fd0cae223dfbd067d9016533d4d4cfedf297a8c92982a02c2e1ebb72583
Timestamp: 1577549893 Timestamp [UTC]: 2019-12-28 16:18:13 Age [y:d:h:m:s]: 06:324:03:58:05
Block: 33610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1645526 RingCT/type: yes/0
Extra: 01a2173fd0cae223dfbd067d9016533d4d4cfedf297a8c92982a02c2e1ebb72583021100000040feadaf7f000000000000000000

1 output(s) for total of 0.474938060973 xmr

stealth address amount amount idx tag
00: 148a389d4e0e31d2c6d6d18e49888a1b59981bbdc403d180bb8a7378152f0f11 0.474938060973 56348 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 dinastycoin-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": 33620, "vin": [ { "gen": { "height": 33610 } } ], "vout": [ { "amount": 474938060973, "target": { "key": "148a389d4e0e31d2c6d6d18e49888a1b59981bbdc403d180bb8a7378152f0f11" } } ], "extra": [ 1, 162, 23, 63, 208, 202, 226, 35, 223, 189, 6, 125, 144, 22, 83, 61, 77, 76, 254, 223, 41, 122, 140, 146, 152, 42, 2, 194, 225, 235, 183, 37, 131, 2, 17, 0, 0, 0, 64, 254, 173, 175, 127, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: