← previous blocknext block →recent activity
Analyzing
Block #106,568,971
28 transactions · 25 stateful · 2026-09-20 21:20:37 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
1.43
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,568,971 · 28 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
1w03w19w010w111w012w013w115w117w118w219w320w421w522w623w724w827w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x110a3804…f842
0x34b655…2a6f
14 touches
21 conflicts
0xc1da8f73…484c
0x34b655…2a6f
8 touches
6 conflicts
0x7fa80a35…9142
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
8 touches
6 conflicts
0x826e9ac2…ad66
0x34b655…2a6f
8 touches
6 conflicts
0x232dd30e…e717
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
21 conflicts on slot 0x110a380404…49f842
Audit this contract →
← previous block·next block →recent activity