← previous blocknext block →recent activity
Analyzing
Block #87,576,984
20 transactions · 15 stateful · 2026-07-13 22:46:33 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,576,984 · 20 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
2w03w14w05w17w09w212w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2607c11…8fa7
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xb568bd0a…0a73
0x34b655…2a6f
4 touches
1 conflict
0xc2f84a16…86b8
0x34b655…2a6f
4 touches
1 conflict
0xda6ebfcf…d51e
0x34b655…2a6f
4 touches
1 conflict
0x1ee4a6d2…6389
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 0xe2607c113c…068fa7
Audit this contract →
← previous block·next block →recent activity