← previous blocknext block →recent activity
Analyzing
Block #86,952,312
23 transactions · 21 stateful · 2026-07-11 01:08:57 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,952,312 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w07w18w29w315w116w317w218w321w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x7babfe9a…ff96
0x34b655…2a6f
6 touches
3 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
6 touches
3 conflicts
0xc7a15219…7745
0xa6afd3…d132
6 touches
3 conflicts
0x4ddc416b…bf17
0x34b655…2a6f
4 touches
1 conflict
0x7b3da897…b268
0x34b655…2a6f
4 touches
1 conflict
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity