← previous blocknext block →recent activity
Analyzing
Block #87,302,697
30 transactions · 23 stateful · 2026-07-12 16:11:25 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,302,697 · 30 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
1w02w13w24w314w016w117w221w322w427w028w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a693a45…747c
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x4a19dcea…c4b9
0xd32edf…ff58
7 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x775a8ad3…8307
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
6 conflicts on slot 0x7a693a4513…8e747c
Audit this contract →
← previous block·next block →recent activity