← previous blocknext block →recent activity
Analyzing
Block #87,488,299
28 transactions · 23 stateful · 2026-07-13 12:52:35 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,488,299 · 28 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
1w02w112w013w114w215w016w120w122w223w327w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2003d8cf…6836
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xb9266685…8b1d
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xc3688185…9b36
0x34b655…2a6f
6 touches
3 conflicts
0x3a6290da…e683
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 0x2003d8cf14…396836
Audit this contract →
← previous block·next block →recent activity