← previous blocknext block →recent activity
Analyzing
Block #87,452,329
22 transactions · 20 stateful · 2026-07-13 08:52:04 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
1.36
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,452,329 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w49w010w111w512w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3fbc9b8…ab58
0x34b655…2a6f
14 touches
21 conflicts
0xc2186704…5cc3
0x34b655…2a6f
10 touches
10 conflicts
0xca18c58e…cede
0x34b655…2a6f
10 touches
10 conflicts
0xe303b183…5413
0x34b655…2a6f
10 touches
10 conflicts
0xf324b405…ca30
0x34b655…2a6f
10 touches
10 conflicts
0x323b1101…aa67
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 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 0xf3fbc9b8fe…77ab58
Audit this contract →
← previous block·next block →recent activity