← previous blocknext block →recent activity
Analyzing
Block #106,235,305
31 transactions · 27 stateful · 2026-09-19 17:21:22 UTC
Parallelism
81/100
Blocked
52%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,235,305 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w17w111w216w017w218w319w421w422w223w324w425w526w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeda80791…093e
0x34b655…2a6f
10 touches
10 conflicts
0x1a84e266…4f8a
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xb550abea…2729
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x4da8c9e8…4e01
0x34b655…2a6f
4 touches
1 conflict
0x676f7b1e…f122
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
10 conflicts on slot 0xeda8079157…f2093e
Audit this contract →
← previous block·next block →recent activity