← previous blocknext block →recent activity
Analyzing
Block #87,055,327
26 transactions · 21 stateful · 2026-07-11 12:37:20 UTC
Parallelism
85/100
Blocked
43%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,055,327 · 26 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
1w05w17w09w011w114w016w117w218w219w320w122w325w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9199a85a…acd9
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x135cdc1d…7b2f
0x34b655…2a6f
6 touches
3 conflicts
0x7d6e48e8…f2b5
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x6bf944a8…4c3d
0xd32edf…ff58
5 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa1940963…fe97
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 0x9199a85ae5…d3acd9
Audit this contract →
← previous block·next block →recent activity