← previous blocknext block →recent activity
Analyzing
Block #87,258,853
11 transactions · 10 stateful · 2026-07-12 11:18:20 UTC
Parallelism
73/100
Blocked
40%
Avg conflicts / tx
0.55
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,258,853 · 11 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
1w02w14w05w06w18w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x015c6c43…fa58
0x34b655…2a6f
4 touches
1 conflict
0x015c6c43…fa59
0x34b655…2a6f
4 touches
1 conflict
0x3ceeaf11…21a8
0x34b655…2a6f
4 touches
1 conflict
0x6dcb5d8d…5f07
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity