← previous blocknext block →recent activity

Analyzing

Block #89,669,035

26 transactions · 23 stateful · 2026-07-23 15:37:31 UTC

Parallelism

73/100

Blocked

35%

Avg conflicts / tx

0.92

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #89,669,035  ·  26 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

0x00000000…0002

0x48cba2…b48b

14 touches
21 conflicts

0x66d5e476…8a1f

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xa6ea029c…6f70

0x158622…375e

2 touches
0 conflicts

0x0c33bb29…c6a9

0x34b655…2a6f

2 touches
0 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

2 touches
0 conflicts

0x326a02b5…8dad

0x34b655…2a6f

2 touches
0 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: 0x48cba278…e2b48b

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity