← previous blocknext block →recent activity
Analyzing
Block #87,710,224
23 transactions · 22 stateful · 2026-07-14 13:37:32 UTC
Parallelism
74/100
Blocked
41%
Avg conflicts / tx
1.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,710,224 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w49w512w013w114w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x727fbce7…0c80
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x2d7ea048…d78e
0x34b655…2a6f
8 touches
6 conflicts
0x2de3014c…0346
0x34b655…2a6f
8 touches
6 conflicts
0x5c3cb0f1…a9fa
0x34b655…2a6f
8 touches
6 conflicts
0x655ebe42…a56a
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 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