← previous blocknext block →recent activity
Analyzing
Block #87,325,075
26 transactions · 24 stateful · 2026-07-12 18:41:06 UTC
Parallelism
62/100
Blocked
63%
Avg conflicts / tx
1.65
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,325,075 · 26 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w17w28w39w410w514w416w517w118w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64aaadbf…f9f3
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x8fdc13c6…f45c
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x671703d0…94b1
0x34b655…2a6f
8 touches
6 conflicts
0xa112f315…1a92
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0x64aaadbf0a…79f9f3
Audit this contract →
← previous block·next block →recent activity