← previous blocknext block →recent activity

Analyzing

Block #89,669,513

20 transactions · 18 stateful · 2026-07-23 15:39:58 UTC

Parallelism

75/100

Blocked

50%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #89,669,513  ·  20 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x803cd43b…b348

0x34b655…2a6f

6 touches
3 conflicts

0x747f609d…1555

0x34b655…2a6f

6 touches
3 conflicts

0x6bd3cf03…b3eb

0x34b655…2a6f

6 touches
3 conflicts

0xc3656cd1…8269

0x34b655…2a6f

6 touches
3 conflicts

0xca30622a…307b

0x065c9d…c394

5 touches
3 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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity