← previous blocknext block →recent activity
Analyzing
Block #89,573,955
35 transactions · 34 stateful · 2026-07-23 05:22:13 UTC
Parallelism
60/100
Blocked
68%
Avg conflicts / tx
2.11
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #89,573,955 · 35 txs across 14 waves · depth 14
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
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w17w38w09w110w211w012w113w214w315w416w517w619w720w322w829w431w1032w1133w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x5502e1cc…3910
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x4886b3df…67a3
0x34b655…2a6f
8 touches
6 conflicts
0x8a55fb33…d776
0xd32edf…ff58
7 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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity