← previous blocknext block →recent activity
Analyzing
Block #87,350,366
22 transactions · 21 stateful · 2026-07-12 21:30:10 UTC
Parallelism
64/100
Blocked
52%
Avg conflicts / tx
1.32
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,350,366 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w48w59w110w611w214w115w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x2ae5c11f…95f3
0x34b655…2a6f
8 touches
6 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
8 touches
6 conflicts
0x131a4489…c12c
0x34b655…2a6f
8 touches
6 conflicts
0x71658d1a…f1ec
0x34b655…2a6f
8 touches
6 conflicts
0x727fbce7…0c80
0x34b655…2a6f
8 touches
6 conflicts
0xada5ad75…1d24
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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity