← previous blocknext block →recent activity
Analyzing
Block #87,120,728
10 transactions · 10 stateful · 2026-07-11 19:54:04 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,120,728 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x496e2285…b499
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1a7
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a0
0xb1dbf0…c0d3
4 touches
1 conflict
0x0d43cc69…6f83
0x34b655…2a6f
4 touches
1 conflict
0x25e3730b…24a9
0x34b655…2a6f
4 touches
1 conflict
0xb95e925b…392d
0x34b655…2a6f
4 touches
1 conflict
0xc368d7fd…aaec
0x34b655…2a6f
4 touches
1 conflict
0xc948dbdc…199a
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 0x496e228536…b4b499
Audit this contract →
← previous block·next block →recent activity