← previous blocknext block →recent activity
Analyzing
Block #106,538,803
24 transactions · 22 stateful · 2026-09-20 18:48:48 UTC
Parallelism
67/100
Blocked
73%
Avg conflicts / tx
2.08
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,538,803 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w38w19w210w311w412w513w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d0e8534…28d2
0x34b655…2a6f
14 touches
21 conflicts
0x67a56c8b…f955
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x3890b9f9…96c6
0x34b655…2a6f
8 touches
6 conflicts
0x6b267bdf…b173
0x34b655…2a6f
8 touches
6 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
8 touches
6 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 0x6d0e85346c…6928d2
Audit this contract →
← previous block·next block →recent activity