← previous blocknext block →recent activity
Analyzing
Block #87,513,088
14 transactions · 13 stateful · 2026-07-13 15:38:30 UTC
Parallelism
57/100
Blocked
46%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,513,088 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w06w17w38w010w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda91bd08…2ef4
0x34b655…2a6f
8 touches
6 conflicts
0xe57232b3…0fbf
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0x1fcf603b…d379
0x34b655…2a6f
4 touches
1 conflict
0x22ce1aa0…6e58
0x34b655…2a6f
4 touches
1 conflict
0x2f702750…347d
0x34b655…2a6f
4 touches
1 conflict
0x35075a55…56b4
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 0xda91bd08e4…582ef4
Audit this contract →
← previous block·next block →recent activity