← previous blocknext block →recent activity
Analyzing
Block #87,708,285
27 transactions · 17 stateful · 2026-07-14 13:24:33 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,708,285 · 27 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
5w010w011w114w116w017w218w119w020w124w125w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0xc31c54de…6133
0x0a2fbf…29b1
4 touches
1 conflict
0xc31c54de…6134
0x0a2fbf…29b1
4 touches
1 conflict
0xe7f560a4…6dbb
0x0a2fbf…29b1
4 touches
1 conflict
0xe7f560a4…6dbc
0x0a2fbf…29b1
4 touches
1 conflict
0xe7f560a4…6dbf
0x0a2fbf…29b1
4 touches
1 conflict
0x31c77e11…2fd8
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 0x1941b4413e…0c5889
Audit this contract →
← previous block·next block →recent activity