← previous blocknext block →recent activity
Analyzing
Block #87,054,711
9 transactions · 9 stateful · 2026-07-11 12:33:13 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,054,711 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25f0d803…174e
0x34b655…2a6f
4 touches
1 conflict
0x25f0d803…174f
0x34b655…2a6f
4 touches
1 conflict
0x5b8a1a43…4aea
0x34b655…2a6f
4 touches
1 conflict
0x79e5df76…64ee
0x34b655…2a6f
4 touches
1 conflict
0xf96f1cdc…d66e
0x34b655…2a6f
4 touches
1 conflict
0xe82f1921…6e42
0x34b655…2a6f
3 touches
1 conflict
0x52000aa6…4ba8
0x065c9d…c394
2 touches
0 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
2 touches
0 conflicts
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
1 conflict on slot 0x25f0d8030d…47174e
Audit this contract →
← previous block·next block →recent activity