← previous blocknext block →recent activity
Analyzing
Block #87,310,390
8 transactions · 6 stateful · 2026-07-12 17:02:51 UTC
Parallelism
38/100
Blocked
67%
Avg conflicts / tx
1.25
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,310,390 · 8 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
1w03w14w25w36w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9f59232…f58c
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xf273c816…7560
0x34b655…2a6f
6 touches
3 conflicts
0x30c0aa06…d479
0x34b655…2a6f
6 touches
3 conflicts
0xc2db6e7a…d074
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x6f5ce1c9…e4ba
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
6 conflicts on slot 0xa9f59232f9…53f58c
Audit this contract →
← previous block·next block →recent activity