← previous blocknext block →recent activity
Analyzing
Block #87,753,419
18 transactions · 14 stateful · 2026-07-14 18:26:38 UTC
Parallelism
56/100
Blocked
57%
Avg conflicts / tx
1.06
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,753,419 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w410w512w613w716w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x747f609d…1555
0x34b655…2a6f
8 touches
6 conflicts
0x2f461725…5ab2
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0xaa643d44…2122
0x34b655…2a6f
8 touches
6 conflicts
0x21c9fd73…dae4
0x34b655…2a6f
8 touches
6 conflicts
0x9fd37234…2731
0x34b655…2a6f
8 touches
6 conflicts
0xc9564a5a…d74b
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity