← previous blocknext block →recent activity
Analyzing
Block #87,287,094
14 transactions · 14 stateful · 2026-07-12 14:27:08 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,287,094 · 14 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
4w05w16w07w18w09w212w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xa559a9f0…e51b
0x0a2fbf…29b1
4 touches
1 conflict
0xa559a9f0…e51c
0x0a2fbf…29b1
4 touches
1 conflict
0xa559a9f0…e51f
0x0a2fbf…29b1
4 touches
1 conflict
0xaecbe638…5008
0x0a2fbf…29b1
4 touches
1 conflict
0xaecbe638…5009
0x0a2fbf…29b1
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x34bcdc05…6689
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
3 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity