← previous blocknext block →recent activity

Analyzing

Block #97,900,768

22 transactions · 19 stateful · 2026-08-21 11:53:29 UTC

Parallelism

82/100

Blocked

37%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,900,768  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x2528e717…2a22

0x34b655…2a6f

6 touches
3 conflicts

0x7de57974…f5ba

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x5e07ca15…c566

0x34b655…2a6f

5 touches
3 conflicts

0x49b0842d…0a93

0x34b655…2a6f

4 touches
1 conflict

0x78d40c9d…1bd0

0x34b655…2a6f

4 touches
1 conflict

0xa7a6c6af…503c

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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

3 conflicts on slot 0x2528e7175c…302a22

← previous block·next block →recent activity