← previous blocknext block →recent activity
Analyzing
Block #87,629,095
22 transactions · 20 stateful · 2026-07-14 04:35:04 UTC
Parallelism
64/100
Blocked
55%
Avg conflicts / tx
1.64
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,629,095 · 22 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
4w05w17w28w39w410w512w315w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
14 touches
21 conflicts
0x32dfa6a9…12f6
0x34b655…2a6f
12 touches
15 conflicts
0x435b08b5…d84e
0x34b655…2a6f
8 touches
6 conflicts
0xd2b87a88…aa57
0x34b655…2a6f
8 touches
6 conflicts
0xa243ce39…3ff4
0x34b655…2a6f
8 touches
6 conflicts
0xfb092633…b7c1
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xb1e4ea6c…3e29
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 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity