← previous blocknext block →recent activity
Analyzing
Block #105,880,889
17 transactions · 16 stateful · 2026-09-18 11:36:31 UTC
Parallelism
47/100
Blocked
50%
Avg conflicts / tx
2.12
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,880,889 · 17 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w38w49w510w611w712w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x297de2d5…7396
0x34b655…2a6f
16 touches
28 conflicts
0x33416595…47c0
0x34b655…2a6f
10 touches
10 conflicts
0x41c52e32…c46a
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
6 touches
3 conflicts
0x6771eae2…7014
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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity