← previous blocknext block →recent activity
Analyzing
Block #87,078,519
25 transactions · 24 stateful · 2026-07-11 15:12:01 UTC
Parallelism
84/100
Blocked
50%
Avg conflicts / tx
0.96
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,078,519 · 25 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
1w02w13w24w38w09w012w113w214w315w116w217w320w021w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xec87cf16…8f99
0xd32edf…ff58
7 touches
6 conflicts
0x76d1e78d…7877
0x40c49f…2af0
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x46005a44…f34b
0xa6afd3…d132
6 touches
3 conflicts
0x824b6de9…7046
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity