← previous blocknext block →recent activity
Analyzing
Block #105,930,077
23 transactions · 20 stateful · 2026-09-18 15:44:59 UTC
Parallelism
83/100
Blocked
55%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,930,077 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w38w29w212w014w116w217w319w021w222w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0x51277ef9…d629
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x17bb579f…938c
0x34b655…2a6f
4 touches
1 conflict
0x1c255088…e409
0x34b655…2a6f
4 touches
1 conflict
0x1c840894…764a
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