← previous blocknext block →recent activity
Analyzing
Block #87,577,189
15 transactions · 13 stateful · 2026-07-13 22:47:55 UTC
Parallelism
67/100
Blocked
46%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,577,189 · 15 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
1w02w13w06w17w08w29w310w211w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xca0f0668…caf3
0xa6afd3…d132
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xb68e226d…c054
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x167de262…f61f
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity