← previous blocknext block →recent activity
Analyzing
Block #87,416,948
12 transactions · 11 stateful · 2026-07-13 04:55:34 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,416,948 · 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
5w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7ca05570…8220
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x9e5adfc8…489d
0x34b655…2a6f
6 touches
3 conflicts
0xac808a27…82db
0x34b655…2a6f
6 touches
3 conflicts
0x199d1f80…72b3
0x34b655…2a6f
4 touches
1 conflict
0x1d946063…ba90
0x34b655…2a6f
4 touches
1 conflict
0x1e9d86f5…53a8
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity