← previous blocknext block →recent activity
Analyzing
Block #106,810,616
18 transactions · 18 stateful · 2026-09-21 17:37:49 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,810,616 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w17w29w112w113w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfdc88ae…d89c
0x34b655…2a6f
12 touches
15 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
8 touches
6 conflicts
0xf90c6521…d8f0
0x34b655…2a6f
8 touches
6 conflicts
0x1e6832ca…0340
0x34b655…2a6f
8 touches
6 conflicts
0xfbb924dd…f2be
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0xcef70a96…db44
0x34b655…2a6f
4 touches
1 conflict
0x4856b443…1824
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 0xdfdc88ae94…84d89c
Audit this contract →
← previous block·next block →recent activity