← previous blocknext block →recent activity

Analyzing

Block #97,478,006

20 transactions · 19 stateful · 2026-08-20 00:04:31 UTC

Parallelism

80/100

Blocked

37%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,478,006  ·  20 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

0xb3fb9fb5…64db

0x34b655…2a6f

8 touches
6 conflicts

0x1293935b…a930

0x34b655…2a6f

6 touches
3 conflicts

0xea1d91a3…b583

0x34b655…2a6f

6 touches
3 conflicts

0xec7d120d…7084

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x469dac8d…3411

0x34b655…2a6f

4 touches
1 conflict

0x6737ee07…9978

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f1

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 0xb3fb9fb561…7664db

← previous block·next block →recent activity