← previous blocknext block →recent activity
Analyzing
Block #87,498,751
52 transactions · 45 stateful · 2026-07-13 14:02:31 UTC
Parallelism
64/100
Blocked
71%
Avg conflicts / tx
4.15
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #87,498,751 · 52 txs across 19 waves · depth 19
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
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w010w213w014w115w220w140w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
34 touches
136 conflicts
0x00000000…00c9
0x34b655…2a6f
26 touches
78 conflicts
0x8cf1f868…c5af
0x34b655…2a6f
18 touches
36 conflicts
0xad0c7701…1d83
0x34b655…2a6f
16 touches
28 conflicts
0x63c900f4…2600
0x34b655…2a6f
16 touches
28 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
16 touches
28 conflicts
0x015c28a0…37da
0x34b655…2a6f
16 touches
28 conflicts
0x5170a218…3a84
0xc8689a…ee79
16 touches
28 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
136 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity