← previous blocknext block →recent activity
Analyzing
Block #87,316,202
12 transactions · 12 stateful · 2026-07-12 17:41:44 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.58
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,316,202 · 12 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
2w03w14w28w09w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1ad
0xb1dbf0…c0d3
5 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9c8812bb…c0f6
0x34b655…2a6f
4 touches
1 conflict
0xa9614018…d6b4
0x34b655…2a6f
4 touches
1 conflict
0xa9f59232…f58c
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity