← previous blocknext block →recent activity

Analyzing

Block #98,531,622

27 transactions · 27 stateful · 2026-08-23 17:00:13 UTC

Parallelism

81/100

Blocked

26%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,531,622  ·  27 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0x7aad02c6…b979

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xebcb0f2d…9305

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xd19c9d38…b459

0x34b655…2a6f

4 touches
1 conflict

0x72470f81…c402

0x34b655…2a6f

4 touches
1 conflict

0xb4b350eb…8c96

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 0xe5bb3628b5…71e5f1

← previous block·next block →recent activity