← previous blocknext block →recent activity
Analyzing
Block #87,078,892
13 transactions · 12 stateful · 2026-07-11 15:14:31 UTC
Parallelism
54/100
Blocked
42%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,078,892 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w37w48w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xc36fa358…24cb
0x34b655…2a6f
10 touches
10 conflicts
0x9b9168c0…f516
0x34b655…2a6f
8 touches
6 conflicts
0xd5c56995…6d22
0x34b655…2a6f
6 touches
3 conflicts
0x5140ab8f…34da
0x34b655…2a6f
6 touches
3 conflicts
0x87a24499…0ad0
0x34b655…2a6f
6 touches
3 conflicts
0x8f2d72a5…5d65
0x34b655…2a6f
6 touches
3 conflicts
0xa1940963…fe97
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity