← previous blocknext block →recent activity
Analyzing
Block #87,582,977
21 transactions · 20 stateful · 2026-07-13 23:26:39 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,582,977 · 21 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
1w02w13w24w07w18w012w115w217w320w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x7314d56d…2b4b
0x34b655…2a6f
6 touches
3 conflicts
0xd5de4c1f…f66e
0xd32edf…ff58
5 touches
3 conflicts
0x21ea036d…5d37
0x34b655…2a6f
4 touches
1 conflict
0x1b89bfcf…8506
0x34b655…2a6f
4 touches
1 conflict
0x4c290b9e…bded
0x34b655…2a6f
4 touches
1 conflict
0x4f1e16d4…4833
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 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity