← previous blocknext block →recent activity
Analyzing
Block #87,319,069
18 transactions · 17 stateful · 2026-07-12 18:00:53 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1.22
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,319,069 · 18 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
1w02w14w05w16w07w28w39w410w512w013w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x727fbce7…0c80
0x34b655…2a6f
10 touches
10 conflicts
0x79d50d4a…951d
0x34b655…2a6f
10 touches
10 conflicts
0x96047c45…b64a
0x34b655…2a6f
10 touches
10 conflicts
0x50718952…7c75
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1aa
0xb1dbf0…c0d3
8 touches
6 conflicts
0x8a35acfb…d1ab
0xb1dbf0…c0d3
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x6bad8d29…b9a0
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
10 conflicts on slot 0x727fbce74b…da0c80
Audit this contract →
← previous block·next block →recent activity