← previous blocknext block →recent activity
Analyzing
Block #87,670,811
24 transactions · 21 stateful · 2026-07-14 09:13:47 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,670,811 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w010w112w013w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd337aaf…cb5e
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x07ed27ca…3903
0x34b655…2a6f
4 touches
1 conflict
0x21c9fd73…dae4
0x34b655…2a6f
4 touches
1 conflict
0x378c030c…a8a4
0x34b655…2a6f
4 touches
1 conflict
0x378c030c…a8a5
0x34b655…2a6f
4 touches
1 conflict
0x3c0c2f32…c3df
0x34b655…2a6f
4 touches
1 conflict
0x536588d3…19c5
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
3 conflicts on slot 0xbd337aafc4…bccb5e
Audit this contract →
← previous block·next block →recent activity