← previous blocknext block →recent activity
Analyzing
Block #87,585,668
20 transactions · 16 stateful · 2026-07-13 23:44:38 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,585,668 · 20 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
2w04w15w28w09w110w211w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa80684c9…3948
0x34b655…2a6f
6 touches
3 conflicts
0x63f8a50d…333b
0x34b655…2a6f
6 touches
3 conflicts
0xc2ee2f56…b6f5
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x410b84ab…1dbc
0x34b655…2a6f
4 touches
1 conflict
0x4303e7ec…ce55
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4d9858eb…7098
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 0xa80684c9ae…1b3948
Audit this contract →
← previous block·next block →recent activity