← previous blocknext block →recent activity
Analyzing
Block #87,878,259
22 transactions · 18 stateful · 2026-07-15 08:21:40 UTC
Parallelism
77/100
Blocked
22%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,878,259 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w09w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebe9512d…5162
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x1fa45507…a954
0x34b655…2a6f
6 touches
3 conflicts
0xff1c6931…7633
0x34b655…2a6f
6 touches
3 conflicts
0xb2e17e09…f30a
0x34b655…2a6f
5 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
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
6 conflicts on slot 0xebe9512db2…265162
Audit this contract →
← previous block·next block →recent activity