← previous blocknext block →recent activity
Analyzing
Block #87,489,068
29 transactions · 23 stateful · 2026-07-13 12:57:43 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,489,068 · 29 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
1w04w16w27w011w014w015w117w218w319w320w426w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xddbb53a9…9198
0x34b655…2a6f
6 touches
3 conflicts
0x31ec17e3…8912
0x34b655…2a6f
6 touches
3 conflicts
0x31ec17e3…8913
0x34b655…2a6f
6 touches
3 conflicts
0x5de7f4e0…c7cd
0x34b655…2a6f
6 touches
3 conflicts
0x6ed9a3c3…001d
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity