← previous blocknext block →recent activity
Analyzing
Block #106,951,705
14 transactions · 14 stateful · 2026-09-22 05:27:59 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,951,705 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w07w08w110w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea79e6d3…68ad
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x4786839b…c29a
0x34b655…2a6f
4 touches
1 conflict
0xce3faf56…82b1
0x34b655…2a6f
4 touches
1 conflict
0x22bee13b…0fa4
0x34b655…2a6f
2 touches
0 conflicts
0x4984f7be…d515
0x34b655…2a6f
2 touches
0 conflicts
0x849a4da4…f503
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
1 conflict on slot 0xea79e6d350…ec68ad
Audit this contract →
← previous block·next block →recent activity