← previous blocknext block →recent activity

Analyzing

Block #89,404,192

20 transactions · 19 stateful · 2026-07-22 10:28:03 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #89,404,192  ·  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

0x5778d110…d2e6

0xc8689a…ee79

6 touches
3 conflicts

0xd6bd849a…5597

0x2a68ba…90c5

6 touches
3 conflicts

0x40970e69…da50

0x2b46c0…1669

6 touches
3 conflicts

0x8cf3d245…1d0d

0x2b46c0…1669

6 touches
3 conflicts

0xb05cd4f5…73d0

0x2b46c0…1669

6 touches
3 conflicts

0xdb067026…9eb8

0x2b46c0…1669

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 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: Settlement / Helper

3 conflicts on slot 0x5778d110c4…8ad2e6

← previous block·next block →recent activity