← previous blocknext block →recent activity
Analyzing
Block #86,493,070
35 transactions · 26 stateful · 2026-07-08 21:57:32 UTC
Parallelism
89/100
Blocked
42%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,493,070 · 35 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
1w02w04w17w08w19w112w013w115w016w117w120w223w225w233w234w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xd9f1e40f…09a3
0x3bd359…433a
6 touches
3 conflicts
0x2877f440…c2c8
0x34b655…2a6f
6 touches
3 conflicts
0x0a49c44b…4b7f
0x34b655…2a6f
6 touches
3 conflicts
0xc948dbdc…199a
0x34b655…2a6f
6 touches
3 conflicts
0x504ac60b…20a6
0x754704…b603
6 touches
3 conflicts
0x527f20e3…82e7
0x754704…b603
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
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
3 conflicts on slot 0x8bf661cb38…d4bcd2
Audit this contract →
← previous block·next block →recent activity