← previous blocknext block →recent activity
Analyzing
Block #105,844,965
24 transactions · 23 stateful · 2026-09-18 08:35:42 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,844,965 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w210w014w116w117w218w319w421w022w123w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf788c790…e66f
0x34b655…2a6f
10 touches
10 conflicts
0xebd9923a…0fe5
0x34b655…2a6f
10 touches
10 conflicts
0xfd7f5b55…4994
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x4d42f16e…a6cd
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x6183ee9a…21b1
0x34b655…2a6f
6 touches
3 conflicts
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 0xf788c79025…f8e66f
Audit this contract →
← previous block·next block →recent activity