← previous blocknext block →recent activity
Analyzing
Block #87,253,718
11 transactions · 7 stateful · 2026-07-12 10:43:56 UTC
Parallelism
64/100
Blocked
57%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,253,718 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w28w19w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c11df38…2f2c
0x34b655…2a6f
6 touches
3 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x6f7775d0…a8b4
0x34b655…2a6f
4 touches
1 conflict
0x17f7e142…085e
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
3 conflicts on slot 0x7c11df389c…6e2f2c
Audit this contract →
← previous block·next block →recent activity