← previous blocknext block →recent activity
Analyzing
Block #106,276,149
25 transactions · 25 stateful · 2026-09-19 20:46:54 UTC
Parallelism
56/100
Blocked
64%
Avg conflicts / tx
1.88
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,276,149 · 25 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w37w38w411w513w615w716w817w918w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd41f5136…97c6
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x46a5ec6c…f318
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x5e2ea201…12de
0x34b655…2a6f
6 touches
3 conflicts
0x8a1c9e92…67b0
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 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
28 conflicts on slot 0xd41f513688…4197c6
Audit this contract →
← previous block·next block →recent activity