Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f96361e59ef87a20575b291b8ab4d41d474fb5a04e551e56185cd5f22e1f8baf

Tx prefix hash: c332b283626195a8caff43bf8a8cb3d894a55b1d3204fb7362d1c00b03d7ac7b
Tx public key: c332a994c17082e63a92e624b3fda31a7aaf64c58d8678f383725361556da7b2
Timestamp: 1658421966 Timestamp [UTC]: 2022-07-21 16:46:06 Age [y:d:h:m:s]: 04:122:05:52:10
Block: 548669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1133543 RingCT/type: yes/0
Extra: 01c332a994c17082e63a92e624b3fda31a7aaf64c58d8678f383725361556da7b202110000000ecb8520c2000000000000000000

1 output(s) for total of 0.009333230119 xmr

stealth address amount amount idx tag
00: bf359a54df707dcfb09f5ef6a345a530a4fdc5f5c9ee2ba5835a47ffb2dc6d06 0.009333230119 979950 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": 548679, "vin": [ { "gen": { "height": 548669 } } ], "vout": [ { "amount": 9333230119, "target": { "key": "bf359a54df707dcfb09f5ef6a345a530a4fdc5f5c9ee2ba5835a47ffb2dc6d06" } } ], "extra": [ 1, 195, 50, 169, 148, 193, 112, 130, 230, 58, 146, 230, 36, 179, 253, 163, 26, 122, 175, 100, 197, 141, 134, 120, 243, 131, 114, 83, 97, 85, 109, 167, 178, 2, 17, 0, 0, 0, 14, 203, 133, 32, 194, 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: