← previous blocknext block →recent activity
Analyzing
Block #87,900,915
35 transactions · 33 stateful · 2026-07-15 10:53:14 UTC
Parallelism
66/100
Blocked
61%
Avg conflicts / tx
1.34
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #87,900,915 · 35 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w18w09w110w011w112w213w314w417w318w219w421w623w724w225w226w329w830w931w1032w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x84585d11…6ae7
0x34b655…2a6f
10 touches
10 conflicts
0x147259c6…1709
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc948dbdc…199a
0x34b655…2a6f
8 touches
6 conflicts
0x0dd44476…ef40
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x30f3ece3…c237
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
10 conflicts on slot 0x84585d11a1…0b6ae7
Audit this contract →
← previous block·next block →recent activity