← previous blocknext block →recent activity
Analyzing
Block #105,856,263
25 transactions · 24 stateful · 2026-09-18 09:32:35 UTC
Parallelism
76/100
Blocked
58%
Avg conflicts / tx
1.32
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,856,263 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w47w58w09w110w211w313w114w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x82462465…4631
0x34b655…2a6f
12 touches
15 conflicts
0xb3aa2022…9e09
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xfefb0189…f726
0x34b655…2a6f
8 touches
6 conflicts
0xab981df1…2941
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x48828733…fd48
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
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
15 conflicts on slot 0x8246246595…f74631
Audit this contract →
← previous block·next block →recent activity