← previous blocknext block →recent activity
Analyzing
Block #87,419,732
20 transactions · 18 stateful · 2026-07-13 05:14:10 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,419,732 · 20 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
1w02w13w04w16w27w38w49w310w012w413w519w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a57a2b8…3cdd
0x34b655…2a6f
8 touches
6 conflicts
0x6e27bdfb…108a
0x34b655…2a6f
6 touches
3 conflicts
0xab360ba6…efc4
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x57e783c1…f03d
0x34b655…2a6f
4 touches
1 conflict
0x5a13f403…8d04
0x34b655…2a6f
4 touches
1 conflict
0x5e4a329f…bc40
0x34b655…2a6f
4 touches
1 conflict
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 0x0a57a2b8cd…773cdd
Audit this contract →
← previous block·next block →recent activity