← previous blocknext block →recent activity
Analyzing
Block #87,287,113
11 transactions · 10 stateful · 2026-07-12 14:27:15 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,287,113 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34bcdc05…6689
0x34b655…2a6f
8 touches
6 conflicts
0x94b8e9d6…77d6
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x3cb4257f…b98d
0x34b655…2a6f
4 touches
1 conflict
0x455bc115…189b
0x34b655…2a6f
4 touches
1 conflict
0x595cbd16…dac4
0x34b655…2a6f
4 touches
1 conflict
0x7734fae8…226e
0x34b655…2a6f
4 touches
1 conflict
0xffd0315e…5316
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 0x34bcdc05ee…2c6689
Audit this contract →
← previous block·next block →recent activity