← previous blocknext block →recent activity
Analyzing
Block #101,309,162
34 transactions · 25 stateful · 2026-09-02 10:51:58 UTC
Parallelism
74/100
Blocked
56%
Avg conflicts / tx
1.06
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #101,309,162 · 34 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
1w04w16w07w08w19w110w112w213w315w416w518w624w525w629w132w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x49339736…b223
0x34b655…2a6f
6 touches
3 conflicts
0x232df012…c608
0x34b655…2a6f
6 touches
3 conflicts
0x5771b06f…14ce
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x88170a77…35f4
0x34b655…2a6f
4 touches
1 conflict
0x91ca1434…4017
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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity