← previous blocknext block →recent activity
Analyzing
Block #87,352,400
16 transactions · 16 stateful · 2026-07-12 21:43:47 UTC
Parallelism
50/100
Blocked
44%
Avg conflicts / tx
1.75
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,352,400 · 16 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
5w06w17w28w39w410w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4ab
0x34b655…2a6f
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0x0733be30…112f
0x34b655…2a6f
14 touches
21 conflicts
0x68761f35…6026
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0xdb3774c5…2442
0x34b655…2a6f
8 touches
6 conflicts
0x59ededb5…45c4
0x34b655…2a6f
6 touches
3 conflicts
0x40080907…45cc
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
28 conflicts on slot 0x7e5ea60ab2…b0c4ab
Audit this contract →
← previous block·next block →recent activity