← previous blocknext block →recent activity
Analyzing
Block #87,355,061
27 transactions · 23 stateful · 2026-07-12 22:01:34 UTC
Parallelism
63/100
Blocked
65%
Avg conflicts / tx
1.89
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,355,061 · 27 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w010w111w212w313w414w515w616w617w721w923w326w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
10 touches
10 conflicts
0x7a11736c…64a0
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
8 touches
6 conflicts
0x4ff21e31…8ed4
0x34b655…2a6f
6 touches
3 conflicts
0x6d85c11e…9c54
0x34b655…2a6f
6 touches
3 conflicts
0x890eac6e…1c0d
0x34b655…2a6f
6 touches
3 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