← previous blocknext block →recent activity
Analyzing
Block #87,252,425
12 transactions · 12 stateful · 2026-07-12 10:35:17 UTC
Parallelism
58/100
Blocked
50%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,252,425 · 12 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
1w02w15w16w27w310w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a5529a7…492e
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
6 touches
3 conflicts
0x42dd9d36…3fc0
0x34b655…2a6f
4 touches
1 conflict
0x4688dd30…ef52
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x57c3fa9e…daa7
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 0x0a5529a751…f8492e
Audit this contract →
← previous block·next block →recent activity