← previous blocknext block →recent activity
Analyzing
Block #87,304,738
10 transactions · 6 stateful · 2026-07-12 16:25:04 UTC
Parallelism
80/100
Blocked
17%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,304,738 · 10 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
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x37ee30c9…9e70
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x05ec65f5…4eff
0x34b655…2a6f
2 touches
0 conflicts
0x077d58c3…8ed7
0x34b655…2a6f
2 touches
0 conflicts
0x3c7908ed…47c8
0x34b655…2a6f
2 touches
0 conflicts
0x6ba89834…1826
0x34b655…2a6f
2 touches
0 conflicts
0x72304467…e18d
0x34b655…2a6f
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity