← previous blocknext block →recent activity
Analyzing
Block #105,843,078
38 transactions · 33 stateful · 2026-09-18 08:26:10 UTC
Parallelism
76/100
Blocked
64%
Avg conflicts / tx
1.55
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,843,078 · 38 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w17w212w215w316w317w418w519w620w721w833w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6003ae26…25c5
0x34b655…2a6f
14 touches
21 conflicts
0xd17580f9…ece1
0x754704…b603
12 touches
15 conflicts
0x206f4379…e08a
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
8 touches
6 conflicts
0x9fa1409b…0e5a
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x0463db49…5d05
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 0x6003ae2677…3f25c5
Audit this contract →
← previous block·next block →recent activity