← previous blocknext block →recent activity
Analyzing
Block #106,801,977
24 transactions · 23 stateful · 2026-09-21 16:54:21 UTC
Parallelism
71/100
Blocked
39%
Avg conflicts / tx
1.04
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,801,977 · 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
1w02w13w24w35w38w49w110w211w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9538417…d2bb
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0x469dac8d…3411
0x34b655…2a6f
6 touches
3 conflicts
0x3cf50d44…961b
0x34b655…2a6f
6 touches
3 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
6 touches
3 conflicts
0x77ca8ee1…e3db
0x34b655…2a6f
6 touches
3 conflicts
0x1011b163…e7dc
0x34b655…2a6f
6 touches
3 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0xa953841765…8ed2bb
Audit this contract →
← previous block·next block →recent activity