← previous blocknext block →recent activity
Analyzing
Block #87,722,479
24 transactions · 22 stateful · 2026-07-14 14:59:39 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,722,479 · 24 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
6w07w18w29w310w411w512w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x5b145de0…367c
0xc8689a…ee79
14 touches
21 conflicts
0x5e4b65e1…ebe1
0x34b655…2a6f
14 touches
21 conflicts
0x67905f6e…02a1
0x34b655…2a6f
14 touches
21 conflicts
0x7525206c…fbd5
0x34b655…2a6f
14 touches
21 conflicts
0x84d74093…7808
0x34b655…2a6f
14 touches
21 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
14 touches
21 conflicts
0x754dd702…1b42
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity