← previous blocknext block →recent activity
Analyzing
Block #86,987,585
30 transactions · 22 stateful · 2026-07-11 05:04:38 UTC
Parallelism
87/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,987,585 · 30 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
5w011w013w017w120w222w126w127w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xbcc5ae85…6ba2
0xa6afd3…d132
4 touches
1 conflict
0x1ebb35bb…ef2a
0x34b655…2a6f
4 touches
1 conflict
0x45877cba…0b50
0x34b655…2a6f
4 touches
1 conflict
0x4e3abeff…18eb
0x34b655…2a6f
4 touches
1 conflict
0x64aaadbf…f9f3
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity