← previous blocknext block →recent activity

Analyzing

Block #89,701,256

19 transactions · 17 stateful · 2026-07-23 18:20:35 UTC

Parallelism

68/100

Blocked

47%

Avg conflicts / tx

1.11

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #89,701,256  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xf2f4727d…cdb7

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0x6f8644f7…10fa

0x34b655…2a6f

4 touches
1 conflict

0x8743e1ba…8331

0x34b655…2a6f

4 touches
1 conflict

0x91f687f3…aca8

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