← previous blocknext block →recent activity
Analyzing
Block #87,518,160
21 transactions · 19 stateful · 2026-07-13 16:12:31 UTC
Parallelism
76/100
Blocked
26%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,518,160 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w19w210w311w413w017w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc335872c…4214
0x34b655…2a6f
6 touches
3 conflicts
0x2b5101ac…090b
0x34b655…2a6f
6 touches
3 conflicts
0x0406a8bb…39a9
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0eac6378…36f4
0x34b655…2a6f
4 touches
1 conflict
0x3f3d0666…5614
0x34b655…2a6f
4 touches
1 conflict
0x5ad8135f…d8e6
0x34b655…2a6f
4 touches
1 conflict
0x799ee783…1f74
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 0xc335872cc4…8e4214
Audit this contract →
← previous block·next block →recent activity