← previous blocknext block →recent activity
Analyzing
Block #87,331,764
12 transactions · 10 stateful · 2026-07-12 19:25:49 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,331,764 · 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
2w05w07w18w210w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0xa055d2b9…fbb6
0x34b655…2a6f
4 touches
1 conflict
0xa243ce39…3ff4
0x34b655…2a6f
4 touches
1 conflict
0xcbe18c62…3a5c
0x34b655…2a6f
4 touches
1 conflict
0xcbe18c62…3a5d
0x34b655…2a6f
4 touches
1 conflict
0xcfe1530d…1249
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity