← previous blocknext block →recent activity
Analyzing
Block #89,379,613
21 transactions · 19 stateful · 2026-07-22 07:43:41 UTC
Parallelism
76/100
Blocked
37%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,379,613 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w010w112w013w114w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x58ad1c46…b729
0x0a2fbf…29b1
4 touches
1 conflict
0x58ad1c46…b72a
0x0a2fbf…29b1
4 touches
1 conflict
0x58ad1c46…b72d
0x0a2fbf…29b1
4 touches
1 conflict
0x9d569648…b02a
0x0a2fbf…29b1
4 touches
1 conflict
0x9d569648…b02b
0x0a2fbf…29b1
4 touches
1 conflict
0x4327afd2…1b3a
0x34b655…2a6f
4 touches
1 conflict
0x6aea3f64…bb1f
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity