← previous blocknext block →recent activity
Analyzing
Block #87,513,675
13 transactions · 12 stateful · 2026-07-13 15:42:26 UTC
Parallelism
62/100
Blocked
50%
Avg conflicts / tx
1.08
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,513,675 · 13 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
1w03w14w05w16w28w311w212w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x60872583…6452
0x34b655…2a6f
6 touches
3 conflicts
0x45449e07…d478
0x34b655…2a6f
4 touches
1 conflict
0x6db97e95…8353
0x34b655…2a6f
4 touches
1 conflict
0x709dde7c…fec4
0x34b655…2a6f
4 touches
1 conflict
0x73bba90b…2eb4
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity