← previous blocknext block →recent activity

Analyzing

Block #89,416,274

20 transactions · 18 stateful · 2026-07-22 11:48:48 UTC

Parallelism

65/100

Blocked

44%

Avg conflicts / tx

0.8

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #89,416,274  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xf1cc9519…84c1

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x63bed776…8d4a

0x34b655…2a6f

4 touches
1 conflict

0x63bed776…8d4b

0x34b655…2a6f

4 touches
1 conflict

0x785705a8…33e5

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity