← previous blocknext block →recent activity

Analyzing

Block #89,694,413

21 transactions · 19 stateful · 2026-07-23 17:46:06 UTC

Parallelism

71/100

Blocked

42%

Avg conflicts / tx

0.62

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #89,694,413  ·  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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x99c5409a…25b7

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x5d46e6a0…5ed9

0x40c49f…2af0

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x465ce74f…39c8

0x34b655…2a6f

4 touches
1 conflict

0x51028c5e…235c

0x34b655…2a6f

4 touches
1 conflict

0x6bc8f55b…7d11

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 0x99c5409a28…0025b7

← previous block·next block →recent activity