← previous blocknext block →recent activity

Analyzing

Block #89,416,313

19 transactions · 16 stateful · 2026-07-22 11:49:04 UTC

Parallelism

58/100

Blocked

50%

Avg conflicts / tx

1.21

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #89,416,313  ·  19 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0x2e095751…39dc

0x34b655…2a6f

4 touches
1 conflict

0x3deaf71f…c229

0x34b655…2a6f

4 touches
1 conflict

0x64ac7e40…5d7d

0x34b655…2a6f

4 touches
1 conflict

0x6b267bdf…b173

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity