← previous blocknext block →recent activity
Analyzing
Block #106,224,485
23 transactions · 21 stateful · 2026-09-19 16:26:51 UTC
Parallelism
74/100
Blocked
48%
Avg conflicts / tx
1.04
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,224,485 · 23 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
1w04w05w19w110w212w013w114w315w216w317w418w521w022w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1d6258c…663e
0x34b655…2a6f
12 touches
15 conflicts
0x746bcce3…d0ce
0x34b655…2a6f
10 touches
10 conflicts
0xb17fc29f…bfad
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x206f4379…e08a
0x34b655…2a6f
6 touches
3 conflicts
0x5c6ab626…997f
0x34b655…2a6f
4 touches
1 conflict
0x638cd0f2…cb93
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
15 conflicts on slot 0xc1d6258cbd…1e663e
Audit this contract →
← previous block·next block →recent activity