← previous blocknext block →recent activity
Analyzing
Block #86,772,755
20 transactions · 15 stateful · 2026-07-10 05:08:50 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,772,755 · 20 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
1w02w17w08w19w212w113w214w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x74550a4b…68bd
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1ad
0xb1dbf0…c0d3
6 touches
3 conflicts
0x87589a70…08bb
0x34b655…2a6f
4 touches
1 conflict
0x98459f89…575d
0x34b655…2a6f
4 touches
1 conflict
0x9cbe5c47…424b
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