← previous blocknext block →recent activity
Analyzing
Block #87,755,231
20 transactions · 17 stateful · 2026-07-14 18:38:45 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,755,231 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w29w311w313w414w518w019w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0dd44476…ef40
0x34b655…2a6f
10 touches
10 conflicts
0x0c20b123…6e84
0x34b655…2a6f
6 touches
3 conflicts
0x04c1c529…0ee1
0x34b655…2a6f
6 touches
3 conflicts
0x22af2e4e…609c
0x34b655…2a6f
6 touches
3 conflicts
0x41fc2b04…2805
0x34b655…2a6f
6 touches
3 conflicts
0x55c2c22c…0474
0x34b655…2a6f
6 touches
3 conflicts
0x6ba89834…1826
0x34b655…2a6f
6 touches
3 conflicts
0x7ab016af…dae9
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0x0dd44476b8…7fef40
Audit this contract →
← previous block·next block →recent activity