← previous blocknext block →recent activity
Analyzing
Block #87,303,807
30 transactions · 29 stateful · 2026-07-12 16:18:51 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,303,807 · 30 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
1w02w13w24w18w09w110w211w312w413w517w018w120w222w328w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0x727fbce7…0c80
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0xe727ab72…768b
0x34b655…2a6f
8 touches
6 conflicts
0x79d50d4a…951d
0x34b655…2a6f
8 touches
6 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
8 touches
6 conflicts
0xa74e1de4…d5bf
0x34b655…2a6f
8 touches
6 conflicts
0xb7050fd7…353c
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
15 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity