← previous blocknext block →recent activity
Analyzing
Block #87,062,797
14 transactions · 13 stateful · 2026-07-11 13:27:10 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,062,797 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w18w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd79c9727…1233
0x34b655…2a6f
4 touches
1 conflict
0xdea31a88…6cfe
0x34b655…2a6f
4 touches
1 conflict
0xdea31a88…6cff
0x34b655…2a6f
4 touches
1 conflict
0xf47128a0…896a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1515ea2e…b538
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
1 conflict on slot 0xd79c972734…f71233
Audit this contract →
← previous block·next block →recent activity