← previous blocknext block →recent activity
Analyzing
Block #106,545,929
24 transactions · 21 stateful · 2026-09-20 19:24:40 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.79
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,545,929 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w28w315w017w020w421w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xddd20e39…d524
0x34b655…2a6f
8 touches
6 conflicts
0x21d22421…0b7a
0x34b655…2a6f
4 touches
1 conflict
0x3643741b…109c
0x34b655…2a6f
4 touches
1 conflict
0x366a19b0…f065
0x34b655…2a6f
4 touches
1 conflict
0x5049717f…a2f6
0x34b655…2a6f
4 touches
1 conflict
0x5a541bec…80fc
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity