← previous blocknext block →recent activity
Analyzing
Block #87,357,244
37 transactions · 34 stateful · 2026-07-12 22:16:09 UTC
Parallelism
62/100
Blocked
79%
Avg conflicts / tx
3.59
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,357,244 · 37 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w15w26w37w211w012w113w214w315w416w517w618w719w820w921w1028w332w433w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
28 touches
91 conflicts
0x8a35acfb…d1ac
0xb1dbf0…c0d3
12 touches
15 conflicts
0xb0bc3bf8…e2b1
0x34b655…2a6f
12 touches
15 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0x63c900f4…2600
0x34b655…2a6f
10 touches
10 conflicts
0x727fbce7…0c80
0x34b655…2a6f
10 touches
10 conflicts
0xc2dda872…7e3e
0x34b655…2a6f
10 touches
10 conflicts
0xdbc62196…3245
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
91 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity