← previous blocknext block →recent activity
Analyzing
Block #89,574,465
21 transactions · 20 stateful · 2026-07-23 05:25:39 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.52
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,574,465 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w09w112w013w117w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf1cc9519…84c1
0x34b655…2a6f
6 touches
3 conflicts
0x0487d7b3…f375
0x34b655…2a6f
4 touches
1 conflict
0x06df379f…2653
0x34b655…2a6f
4 touches
1 conflict
0x20081203…b191
0x34b655…2a6f
4 touches
1 conflict
0x21d8211e…df64
0x34b655…2a6f
4 touches
1 conflict
0x24b6091e…d294
0x34b655…2a6f
4 touches
1 conflict
0x2b8d9898…d525
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity