← previous blocknext block →recent activity
Analyzing
Block #87,078,084
18 transactions · 16 stateful · 2026-07-11 15:09:06 UTC
Parallelism
61/100
Blocked
69%
Avg conflicts / tx
1.44
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,078,084 · 18 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
1w02w13w04w15w26w37w48w59w610w112w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
10 touches
10 conflicts
0xd3ef5630…0de9
0x34b655…2a6f
10 touches
10 conflicts
0xf4b003cb…9225
0x34b655…2a6f
10 touches
10 conflicts
0xf7e59d30…11dd
0x34b655…2a6f
10 touches
10 conflicts
0xf9086bec…573c
0x34b655…2a6f
10 touches
10 conflicts
0x1175233a…64e7
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity