← previous blocknext block →recent activity

Analyzing

Block #89,736,327

8 transactions · 8 stateful · 2026-07-23 21:17:36 UTC

Parallelism

63/100

Blocked

25%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,736,327  ·  8 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x55b4e430…44cb

0x754704…b603

6 touches
3 conflicts

0x00000000…0006

0x0a2fbf…29b1

6 touches
3 conflicts

0x9d3695ed…9176

0x0a2fbf…29b1

4 touches
1 conflict

0x1bff683e…7ecb

0x754704…b603

4 touches
1 conflict

0x9d3695ed…9173

0x0a2fbf…29b1

4 touches
1 conflict

0x00000000…0005

0x370e2e…63b4

4 touches
1 conflict

0x9d3695ed…9172

0x0a2fbf…29b1

4 touches
1 conflict

0x06e40499…165e

0x2b46c0…1669

2 touches
0 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: USDC (USDC)

3 conflicts on slot 0x55b4e430de…d044cb

← previous block·next block →recent activity