← previous blocknext block →recent activity
Analyzing
Block #87,489,324
16 transactions · 15 stateful · 2026-07-13 12:59:27 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,489,324 · 16 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
1w02w13w26w07w18w09w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x88adad52…54b7
0x34b655…2a6f
6 touches
3 conflicts
0x4c04ce68…d007
0x34b655…2a6f
4 touches
1 conflict
0x5a13f403…8d04
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x766ecb55…cea4
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity