← previous blocknext block →recent activity

Analyzing

Block #97,828,511

23 transactions · 18 stateful · 2026-08-21 05:42:14 UTC

Parallelism

74/100

Blocked

39%

Avg conflicts / tx

0.65

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #97,828,511  ·  23 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

0xe5bb3628…e5f1

0x34b655…2a6f

10 touches
10 conflicts

0x5539e38d…d3d2

0x34b655…2a6f

8 touches
6 conflicts

0x9ae859db…2d84

0x34b655…2a6f

6 touches
3 conflicts

0xc21a060b…d1f1

0x34b655…2a6f

6 touches
3 conflicts

0x7aad02c6…b979

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x36a76bd2…1fb0

0x34b655…2a6f

4 touches
1 conflict

0x438f4336…47c9

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

10 conflicts on slot 0xe5bb3628b5…71e5f1

← previous block·next block →recent activity