← previous blocknext block →recent activity
Analyzing
Block #106,184,804
25 transactions · 21 stateful · 2026-09-19 13:07:06 UTC
Parallelism
72/100
Blocked
52%
Avg conflicts / tx
1.12
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,184,804 · 25 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
1w05w08w110w111w112w214w315w316w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe5f5aab…21d7
0x34b655…2a6f
14 touches
21 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
10 touches
10 conflicts
0x07c47b1c…93c8
0x34b655…2a6f
6 touches
3 conflicts
0x000bde1a…e123
0x34b655…2a6f
6 touches
3 conflicts
0x4786839b…c29a
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc09c3422…3c8b
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
21 conflicts on slot 0xfe5f5aab0c…ba21d7
Audit this contract →
← previous block·next block →recent activity