← previous blocknext block →recent activity
Analyzing
Block #87,524,962
14 transactions · 13 stateful · 2026-07-13 16:58:30 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,524,962 · 14 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
1w03w04w15w16w29w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x24f6d4ca…c33b
0x34b655…2a6f
6 touches
3 conflicts
0x1cbe4f94…3a9b
0x34b655…2a6f
4 touches
1 conflict
0xa207048b…6a7e
0x5a66a5…cba8
4 touches
1 conflict
0x00000000…0003
0x98a45d…206a
4 touches
1 conflict
0xaeb46f64…7cfc
0xaca92e…35da
4 touches
1 conflict
0xbb02d03d…5383
0xaca92e…35da
4 touches
1 conflict
0xcb355338…c9a5
0xaca92e…35da
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity