← previous blocknext block →recent activity
Analyzing
Block #94,841,206
56 transactions · 52 stateful · 2026-08-10 18:00:18 UTC
Parallelism
71/100
Blocked
73%
Avg conflicts / tx
3.07
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #94,841,206 · 56 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w28w09w010w111w112w213w214w315w426w427w536w138w939w240w241w342w446w448w150w1051w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
14 touches
21 conflicts
0x734ee320…caae
0x34b655…2a6f
14 touches
21 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
12 touches
15 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xb39cb1d8…effa
0x34b655…2a6f
10 touches
10 conflicts
0xd30f9e74…d404
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity