← previous blocknext block →recent activity
Analyzing
Block #105,922,632
24 transactions · 23 stateful · 2026-09-18 15:07:30 UTC
Parallelism
75/100
Blocked
52%
Avg conflicts / tx
1.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,922,632 · 24 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
1w02w13w05w06w07w19w210w315w416w518w119w220w421w523w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23b2399c…6e4b
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x045532dd…4b7d
0x34b655…2a6f
6 touches
3 conflicts
0x159d9381…fd9b
0x34b655…2a6f
6 touches
3 conflicts
0x3a429191…9cda
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
10 conflicts on slot 0x23b2399ccb…706e4b
Audit this contract →
← previous block·next block →recent activity