← previous blocknext block →recent activity
Analyzing
Block #87,264,074
10 transactions · 9 stateful · 2026-07-12 11:53:11 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,264,074 · 10 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
1w02w13w05w16w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4688dd30…ef52
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xf81d0d0f…cf78
0x34b655…2a6f
4 touches
1 conflict
0x0dd44476…ef40
0x34b655…2a6f
4 touches
1 conflict
0xd4f1ce47…f31d
0xd32edf…ff58
3 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
2 touches
0 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
1 conflict on slot 0x4688dd309c…31ef52
Audit this contract →
← previous block·next block →recent activity