← previous blocknext block →recent activity
Analyzing
Block #106,551,198
10 transactions · 10 stateful · 2026-09-20 19:51:10 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,551,198 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w08w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07c47b1c…93c8
0x34b655…2a6f
6 touches
3 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
4 touches
1 conflict
0xc3513eac…42db
0x34b655…2a6f
4 touches
1 conflict
0xc5f336ca…912e
0x34b655…2a6f
4 touches
1 conflict
0xe22ab637…7a8e
0x34b655…2a6f
4 touches
1 conflict
0x3b6e959d…158f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
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
3 conflicts on slot 0x07c47b1ce2…b693c8
Audit this contract →
← previous block·next block →recent activity