Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf0f9535d174f0d8ec184f016d903165437d4ccf00992d34d9037510aa01f0e9

Tx prefix hash: e2ff0a889be3d16cdf14020b23d80908cfd632e04453fd970fb753aaa4c03921
Tx public key: 3f3ed2b2a4847f511d89b47659ef0e8a16439997d013aeb4f416ec031288d1c6
Timestamp: 1583344426 Timestamp [UTC]: 2020-03-04 17:53:46 Age [y:d:h:m:s]: 06:070:22:24:25
Block: 76053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1456906 RingCT/type: yes/0
Extra: 013f3ed2b2a4847f511d89b47659ef0e8a16439997d013aeb4f416ec031288d1c60211000000017adf42d3000000000000000000

1 output(s) for total of 0.343562406113 xmr

stealth address amount amount idx tag
00: f1208bf0d49dc82d8fe28b4b2cb9415b59eb7580a0348f780cdd7dd862b4252a 0.343562406113 140269 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": 76063, "vin": [ { "gen": { "height": 76053 } } ], "vout": [ { "amount": 343562406113, "target": { "key": "f1208bf0d49dc82d8fe28b4b2cb9415b59eb7580a0348f780cdd7dd862b4252a" } } ], "extra": [ 1, 63, 62, 210, 178, 164, 132, 127, 81, 29, 137, 180, 118, 89, 239, 14, 138, 22, 67, 153, 151, 208, 19, 174, 180, 244, 22, 236, 3, 18, 136, 209, 198, 2, 17, 0, 0, 0, 1, 122, 223, 66, 211, 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: