← previous blocknext block →recent activity
Analyzing
Block #87,723,348
30 transactions · 23 stateful · 2026-07-14 15:05:28 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,723,348 · 30 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
2w011w112w213w316w017w119w220w021w322w123w224w326w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64a058c6…74a1
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7525206c…fbd5
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x6f16ce74…1910
0x34b655…2a6f
4 touches
1 conflict
0x84d74093…7808
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 0x64a058c6c8…5774a1
Audit this contract →
← previous block·next block →recent activity