← previous blocknext block →recent activity
Analyzing
Block #87,585,623
22 transactions · 16 stateful · 2026-07-13 23:44:20 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,585,623 · 22 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
1w02w13w07w18w214w016w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17cc5ec3…ae0e
0x34b655…2a6f
6 touches
3 conflicts
0x04c1786f…3ee6
0x34b655…2a6f
4 touches
1 conflict
0x20ff72d4…5971
0x34b655…2a6f
4 touches
1 conflict
0x25a19347…5424
0x34b655…2a6f
4 touches
1 conflict
0x2e64e234…5cfa
0x34b655…2a6f
4 touches
1 conflict
0x3259db2f…a6a0
0x34b655…2a6f
4 touches
1 conflict
0x366c7d57…0ed1
0x34b655…2a6f
4 touches
1 conflict
0x3a61096b…5107
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 0x17cc5ec39e…57ae0e
Audit this contract →
← previous block·next block →recent activity