← previous blocknext block →recent activity
Analyzing
Block #86,812,159
25 transactions · 22 stateful · 2026-07-10 09:31:55 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,812,159 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
11w015w016w117w118w219w322w023w124w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xa100c256…fb30
0x34b655…2a6f
6 touches
3 conflicts
0xca57a4ab…b781
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x78d79dcd…a930
0x34b655…2a6f
6 touches
3 conflicts
0x4bd41fd9…4194
0x34b655…2a6f
6 touches
3 conflicts
0x73a951a2…53db
0x34b655…2a6f
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity