← previous blocknext block →recent activity
Analyzing
Block #87,729,232
15 transactions · 15 stateful · 2026-07-14 15:44:51 UTC
Parallelism
47/100
Blocked
47%
Avg conflicts / tx
1.53
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,729,232 · 15 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
3w04w15w26w39w410w511w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x67905f6e…02a1
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
8 touches
6 conflicts
0xa55c4598…2988
0x34b655…2a6f
8 touches
6 conflicts
0x4ca1448c…9de6
0x34b655…2a6f
8 touches
6 conflicts
0x312e4698…54c0
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4a3
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity