← previous blocknext block →recent activity
Analyzing
Block #87,869,897
27 transactions · 24 stateful · 2026-07-15 07:25:44 UTC
Parallelism
81/100
Blocked
42%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,869,897 · 27 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
1w02w13w24w05w17w09w112w113w217w218w320w425w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x155dff63…2af8
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…000b
0x90c374…be45
6 touches
3 conflicts
0x00000000…000a
0x90c374…be45
6 touches
3 conflicts
0x1a287886…0266
0xa6afd3…d132
6 touches
3 conflicts
0x1803586e…d149
0xa6afd3…d132
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 0x155dff638e…a62af8
Audit this contract →
← previous block·next block →recent activity