← previous blocknext block →recent activity
Analyzing
Block #87,265,441
17 transactions · 16 stateful · 2026-07-12 12:02:18 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
1.12
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,265,441 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w29w010w211w312w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x722851f4…73fe
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x00476ad5…38b5
0xd32edf…ff58
5 touches
3 conflicts
0x6c68ddc9…d106
0xb1dbf0…c0d3
5 touches
3 conflicts
0x8a35acfb…d1ab
0xb1dbf0…c0d3
5 touches
3 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
6 conflicts on slot 0x722851f4b1…4173fe
Audit this contract →
← previous block·next block →recent activity