← previous blocknext block →recent activity
Analyzing
Block #87,724,358
15 transactions · 14 stateful · 2026-07-14 15:12:14 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,724,358 · 15 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
1w02w13w05w17w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5ea108a…dbf6
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a4
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xa0ebadea…4145
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbc6cae40…7e2f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641c
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
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
1 conflict on slot 0xf5ea108a6a…e5dbf6
Audit this contract →
← previous block·next block →recent activity