← previous blocknext block →recent activity

Analyzing

Block #97,627,833

21 transactions · 19 stateful · 2026-08-20 12:41:16 UTC

Parallelism

86/100

Blocked

26%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #97,627,833  ·  21 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

0xa8eeba75…91c7

0x34b655…2a6f

6 touches
3 conflicts

0x6aa7a878…0103

0xa6afd3…d132

4 touches
1 conflict

0x00f245ce…1e10

0x34b655…2a6f

4 touches
1 conflict

0x214dc988…ba27

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xccebf5c5…8758

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 0xa8eeba7535…f691c7

← previous block·next block →recent activity