← previous blocknext block →recent activity

Analyzing

Block #89,690,394

20 transactions · 20 stateful · 2026-07-23 17:25:50 UTC

Parallelism

70/100

Blocked

45%

Avg conflicts / tx

1.05

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #89,690,394  ·  20 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x57070322…bc66

0xe52b14…7230

12 touches
15 conflicts

0x8ffa3328…ce11

0xe52b14…7230

12 touches
15 conflicts

0xf79df061…e005

0xe52b14…7230

12 touches
15 conflicts

0xaba34ac8…96d4

0xe52b14…7230

11 touches
15 conflicts

0x0b0c2e8d…c1b8

0xe52b14…7230

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x61a354cc…15c9

0xe52b14…7230

4 touches
1 conflict

0x09dddc76…e12a

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: 0xe52b1424…bb7230

15 conflicts on slot 0x570703220d…6ebc66

← previous block·next block →recent activity