← previous blocknext block →recent activity
Analyzing
Block #87,750,127
24 transactions · 24 stateful · 2026-07-14 18:04:38 UTC
Parallelism
54/100
Blocked
58%
Avg conflicts / tx
2.25
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,750,127 · 24 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w17w28w39w410w511w612w715w616w217w522w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x0dd44476…ef40
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x1d9c7a35…ea9d
0x34b655…2a6f
8 touches
6 conflicts
0x4cee015b…1a5e
0x34b655…2a6f
8 touches
6 conflicts
0x5eb5d9be…b2c1
0x34b655…2a6f
8 touches
6 conflicts
0x64800813…db9f
0x34b655…2a6f
8 touches
6 conflicts
0x6e90b9b1…dca8
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity