← previous blocknext block →recent activity
Analyzing
Block #87,328,630
12 transactions · 11 stateful · 2026-07-12 19:04:51 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,328,630 · 12 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
1w04w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf852da67…e76b
0x34b655…2a6f
4 touches
1 conflict
0xf522dc60…a709
0x34b655…2a6f
4 touches
1 conflict
0xf60d3c80…c8a7
0x34b655…2a6f
4 touches
1 conflict
0x16898f19…955d
0x34b655…2a6f
4 touches
1 conflict
0x1bee5aea…5f61
0x34b655…2a6f
4 touches
1 conflict
0x6b564d99…b9eb
0x34b655…2a6f
4 touches
1 conflict
0x6b564d99…b9ec
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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
1 conflict on slot 0xf852da678d…73e76b
Audit this contract →
← previous block·next block →recent activity