← previous blocknext block →recent activity
Analyzing
Block #106,930,848
24 transactions · 22 stateful · 2026-09-22 03:43:00 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,930,848 · 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
2w03w15w06w19w010w111w212w313w415w316w517w618w722w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0463db49…5d05
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
10 touches
10 conflicts
0xe7e580a2…39ed
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0xf782ee27…41cd
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x28ca6536…38d6
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 0x0463db492b…795d05
Audit this contract →
← previous block·next block →recent activity