← previous blocknext block →recent activity
Analyzing
Block #87,517,948
29 transactions · 23 stateful · 2026-07-13 16:11:05 UTC
Parallelism
90/100
Blocked
35%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,517,948 · 29 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
1w03w06w17w110w012w013w118w020w121w122w223w227w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f068b13…fb19
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xa19aba84…8922
0xa6afd3…d132
6 touches
3 conflicts
0x25329a48…4e00
0x34b655…2a6f
4 touches
1 conflict
0x3863eb34…c4e5
0x34b655…2a6f
4 touches
1 conflict
0x3c7e8bf1…5c68
0x34b655…2a6f
4 touches
1 conflict
0x5c220a16…7bde
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 0x0f068b130e…d0fb19
Audit this contract →
← previous block·next block →recent activity