← previous blocknext block →recent activity
Analyzing
Block #106,539,008
19 transactions · 15 stateful · 2026-09-20 18:49:50 UTC
Parallelism
68/100
Blocked
40%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,539,008 · 19 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
6w07w09w111w212w313w414w518w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ac18b8d…0c1c
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x38c6ff01…689f
0x34b655…2a6f
8 touches
6 conflicts
0xaa3b4402…74e6
0x34b655…2a6f
8 touches
6 conflicts
0x8fcbf9b2…a36e
0x34b655…2a6f
8 touches
6 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
6 touches
3 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
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 0x8ac18b8d23…920c1c
Audit this contract →
← previous block·next block →recent activity