← previous blocknext block →recent activity
Analyzing
Block #87,730,232
39 transactions · 32 stateful · 2026-07-14 15:51:32 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
1.23
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,730,232 · 39 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
1w03w16w09w010w111w215w016w117w218w319w420w521w622w726w227w336w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
12 touches
15 conflicts
0x3c0c2f32…c3df
0x34b655…2a6f
12 touches
15 conflicts
0x67905f6e…02a1
0x34b655…2a6f
12 touches
15 conflicts
0x8d4c0bb9…ccd3
0x34b655…2a6f
12 touches
15 conflicts
0xc4de6652…13f4
0x34b655…2a6f
12 touches
15 conflicts
0xfd5942ee…c2da
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity