← previous blocknext block →recent activity
Analyzing
Block #102,205,783
25 transactions · 23 stateful · 2026-09-05 14:15:03 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.96
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,205,783 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w07w18w09w210w315w418w221w123w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdf409966…6b16
0x3bd359…433a
10 touches
10 conflicts
0x5b0621ee…3c2c
0x284f45…7777
10 touches
10 conflicts
0xa164d951…1534
0xe1c8b7…3022
10 touches
10 conflicts
0x4eb758b8…b13b
0x3bd359…433a
10 touches
10 conflicts
0x00000000…0004
0x7aed55…0617
10 touches
10 conflicts
0xd868fb65…3b4a
0xe1c8b7…3022
9 touches
10 conflicts
0xf58eca50…59fd
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Wrapped MON (WMON)
10 conflicts on slot 0xdf40996690…8c6b16
Audit this contract →
← previous block·next block →recent activity