← previous blocknext block →recent activity
Analyzing
Block #87,524,931
28 transactions · 21 stateful · 2026-07-13 16:58:17 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,524,931 · 28 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
1w02w03w04w011w013w114w115w220w321w322w125w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24f6d4ca…c33b
0x34b655…2a6f
8 touches
6 conflicts
0x53f393fa…00b9
0x34b655…2a6f
6 touches
3 conflicts
0x3a6290da…e683
0x34b655…2a6f
6 touches
3 conflicts
0x274ac476…27fa
0x34b655…2a6f
4 touches
1 conflict
0x3db35c09…f26c
0x34b655…2a6f
4 touches
1 conflict
0x4688dd30…ef52
0x34b655…2a6f
4 touches
1 conflict
0x4c188934…158e
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x24f6d4ca30…1ec33b
Audit this contract →
← previous block·next block →recent activity