← previous blocknext block →recent activity
Analyzing
Block #87,286,671
10 transactions · 10 stateful · 2026-07-12 14:24:18 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,286,671 · 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34bcdc05…6689
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x5ed58b36…c5e5
0x34b655…2a6f
4 touches
1 conflict
0x3c7908ed…47c8
0x34b655…2a6f
4 touches
1 conflict
0x29064bbf…10f0
0x34b655…2a6f
2 touches
0 conflicts
0x2b588dd8…a5b6
0x34b655…2a6f
2 touches
0 conflicts
0x3be33cca…1000
0x34b655…2a6f
2 touches
0 conflicts
0x3f0375e5…a8a2
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 0x34bcdc05ee…2c6689
Audit this contract →
← previous block·next block →recent activity