← previous blocknext block →recent activity
Analyzing
Block #105,857,853
16 transactions · 15 stateful · 2026-09-18 09:40:35 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,857,853 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w59w610w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f8107c4…9cb2
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x8db32935…81a7
0x34b655…2a6f
8 touches
6 conflicts
0xf06fce24…887d
0x34b655…2a6f
6 touches
3 conflicts
0x80398c66…f3cc
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x1aefc3d2…66f5
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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
21 conflicts on slot 0x7f8107c498…8a9cb2
Audit this contract →
← previous block·next block →recent activity