← previous blocknext block →recent activity
Analyzing
Block #105,852,320
28 transactions · 26 stateful · 2026-09-18 09:12:44 UTC
Parallelism
75/100
Blocked
54%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,852,320 · 28 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
1w02w13w24w35w17w210w316w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2229f653…8c8b
0x34b655…2a6f
14 touches
21 conflicts
0x831f75b4…945d
0x34b655…2a6f
12 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
8 touches
6 conflicts
0x95ed91b3…27c8
0xd32edf…ff58
7 touches
6 conflicts
0x3e04662b…0da8
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x7c51d9aa…af39
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
21 conflicts on slot 0x2229f65300…f88c8b
Audit this contract →
← previous block·next block →recent activity