← previous blocknext block →recent activity
Analyzing
Block #87,518,270
15 transactions · 13 stateful · 2026-07-13 16:13:15 UTC
Parallelism
73/100
Blocked
31%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,518,270 · 15 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
4w05w16w27w310w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e49f754…23a2
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x14c5407b…4a40
0x34b655…2a6f
6 touches
3 conflicts
0x1c4970af…8823
0x34b655…2a6f
6 touches
3 conflicts
0x293fed86…ed95
0x34b655…2a6f
6 touches
3 conflicts
0x35d95fb0…db9e
0x34b655…2a6f
6 touches
3 conflicts
0x35d95fb0…db9f
0x34b655…2a6f
6 touches
3 conflicts
0x461428a9…24b2
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 0x9e49f754f7…be23a2
Audit this contract →
← previous block·next block →recent activity