← previous blocknext block →recent activity
Analyzing
Block #87,716,782
24 transactions · 21 stateful · 2026-07-14 14:21:34 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,716,782 · 24 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
5w06w17w08w111w013w114w217w219w320w322w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c591136…d322
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x307414a5…7214
0x34b655…2a6f
6 touches
3 conflicts
0x3de775b2…319b
0xa6afd3…d132
6 touches
3 conflicts
0xfa551be3…a911
0xa6afd3…d132
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2c3f67c8…40c9
0x34b655…2a6f
4 touches
1 conflict
0x2f7ef34f…4ec4
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 0x5c591136e9…b7d322
Audit this contract →
← previous block·next block →recent activity