← previous blocknext block →recent activity
Analyzing
Block #87,357,148
15 transactions · 13 stateful · 2026-07-12 22:15:30 UTC
Parallelism
73/100
Blocked
69%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,357,148 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w15w06w17w28w311w112w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x01c5e0ea…3908
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x4a5df61e…a961
0x34b655…2a6f
6 touches
3 conflicts
0x526b2642…298c
0x34b655…2a6f
6 touches
3 conflicts
0x57963d88…0897
0x34b655…2a6f
6 touches
3 conflicts
0x60d7fd08…a37e
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity