← previous blocknext block →recent activity
Analyzing
Block #106,952,050
24 transactions · 24 stateful · 2026-09-22 05:29:44 UTC
Parallelism
71/100
Blocked
54%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,952,050 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w16w19w210w011w112w214w217w318w419w520w621w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3eb48ea2…eef2
0x34b655…2a6f
10 touches
10 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
10 touches
10 conflicts
0x61155067…cec4
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
6 touches
3 conflicts
0xb7aa9720…56df
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 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: Perpl
10 conflicts on slot 0x3eb48ea2b8…b6eef2
Audit this contract →
← previous block·next block →recent activity