← previous blocknext block →recent activity
Analyzing
Block #87,592,321
28 transactions · 24 stateful · 2026-07-14 00:29:07 UTC
Parallelism
75/100
Blocked
54%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,592,321 · 28 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w06w17w28w39w410w513w218w121w626w427w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x421280e8…c400
0x40c49f…2af0
6 touches
3 conflicts
0x0eeb2a30…6909
0x34b655…2a6f
6 touches
3 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x757057f2…8eed
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity