← previous blocknext block →recent activity

Analyzing

Block #89,748,397

17 transactions · 17 stateful · 2026-07-23 22:18:36 UTC

Parallelism

82/100

Blocked

29%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,748,397  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xf79df061…e005

0xe52b14…7230

4 touches
1 conflict

0x9a73834c…0f52

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xc60a1f10…d727

0x34b655…2a6f

4 touches
1 conflict

0xcb39ee88…f896

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x5311f864…0984

0x754704…b603

4 touches
1 conflict

0x0b0c2e8d…c1b8

0xe52b14…7230

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: 0xe52b1424…bb7230

1 conflict on slot 0xf79df061c7…91e005

← previous block·next block →recent activity