← previous blocknext block →recent activity
Analyzing
Block #105,852,428
28 transactions · 26 stateful · 2026-09-18 09:13:17 UTC
Parallelism
75/100
Blocked
62%
Avg conflicts / tx
1.39
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,852,428 · 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
1w02w13w14w25w06w17w210w112w318w219w322w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf20480f8…8620
0x34b655…2a6f
8 touches
6 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x1033ac83…3fc5
0x34b655…2a6f
8 touches
6 conflicts
0x89999c15…fdac
0x34b655…2a6f
8 touches
6 conflicts
0xab981df1…2941
0x34b655…2a6f
8 touches
6 conflicts
0xb10ef1bb…022b
0x34b655…2a6f
8 touches
6 conflicts
0x105b8684…2dcf
0xd32edf…ff58
7 touches
6 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
6 conflicts on slot 0xf20480f87f…af8620
Audit this contract →
← previous block·next block →recent activity