← previous blocknext block →recent activity
Analyzing
Block #87,791,194
56 transactions · 44 stateful · 2026-07-14 22:39:21 UTC
Parallelism
68/100
Blocked
70%
Avg conflicts / tx
2.02
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #87,791,194 · 56 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w212w013w117w019w120w221w322w429w334w235w337w1038w339w440w542w644w748w1250w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xe2e52e46…0894
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0x5d46e6a0…5ed9
0x40c49f…2af0
10 touches
10 conflicts
0x76d1e78d…7877
0x40c49f…2af0
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xc91d4275…1d7c
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity