← previous blocknext block →recent activity
Analyzing
Block #87,285,440
19 transactions · 19 stateful · 2026-07-12 14:16:04 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
1.16
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,285,440 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w09w413w115w518w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
10 touches
10 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
8 touches
6 conflicts
0x0c437c9b…1bb2
0x34b655…2a6f
8 touches
6 conflicts
0x66f7b1ee…a38b
0x34b655…2a6f
8 touches
6 conflicts
0xaba6578d…bd48
0x34b655…2a6f
8 touches
6 conflicts
0xaedc3dd6…3c3b
0x34b655…2a6f
8 touches
6 conflicts
0xd58e5c6b…7188
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity