← previous blocknext block →recent activity
Analyzing
Block #105,849,732
23 transactions · 22 stateful · 2026-09-18 08:59:43 UTC
Parallelism
70/100
Blocked
55%
Avg conflicts / tx
1.57
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,849,732 · 23 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
1w02w05w16w28w311w212w213w314w415w516w622w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd63857dd…6d47
0x34b655…2a6f
14 touches
21 conflicts
0x80398c66…f3cc
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x2827ae77…4368
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xcd5c0ecb…4b5f
0x34b655…2a6f
6 touches
3 conflicts
0xc10b903d…2f54
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
21 conflicts on slot 0xd63857dd2f…bc6d47
Audit this contract →
← previous block·next block →recent activity