← previous blocknext block →recent activity

Analyzing

Block #89,377,248

19 transactions · 18 stateful · 2026-07-22 07:27:52 UTC

Parallelism

53/100

Blocked

56%

Avg conflicts / tx

1.58

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #89,377,248  ·  19 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

12 touches
15 conflicts

0xcc351d6d…256b

0x34b655…2a6f

8 touches
6 conflicts

0x42bb0ac5…6b33

0x34b655…2a6f

6 touches
3 conflicts

0xf1cc9519…84c1

0x34b655…2a6f

6 touches
3 conflicts

0x2546c113…3198

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity