← previous blocknext block →recent activity
Analyzing
Block #87,452,090
34 transactions · 28 stateful · 2026-07-13 08:50:28 UTC
Parallelism
76/100
Blocked
61%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,452,090 · 34 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
1w02w13w04w18w29w310w011w112w013w114w215w316w417w318w420w521w622w423w524w632w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xa0d3a786…91d9
0x34b655…2a6f
10 touches
10 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
8 touches
6 conflicts
0x0090639e…243e
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity