← previous blocknext block →recent activity
Analyzing
Block #106,934,455
20 transactions · 19 stateful · 2026-09-22 04:01:09 UTC
Parallelism
75/100
Blocked
32%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,934,455 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w08w111w012w113w214w315w417w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0x8d5fc820…1750
0x34b655…2a6f
10 touches
10 conflicts
0x3d4ceda4…84c4
0x34b655…2a6f
10 touches
10 conflicts
0xf7b76d2f…1b9c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x3347cbe5…846c
0x34b655…2a6f
2 touches
0 conflicts
0x68c740e2…58d6
0x34b655…2a6f
2 touches
0 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
10 conflicts on slot 0xccebf5c5cb…c88758
Audit this contract →
← previous block·next block →recent activity