← previous blocknext block →recent activity

Analyzing

Block #97,991,376

19 transactions · 18 stateful · 2026-08-21 19:34:24 UTC

Parallelism

79/100

Blocked

33%

Avg conflicts / tx

0.37

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,991,376  ·  19 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xcaa5e459…c7eb

0x34b655…2a6f

4 touches
1 conflict

0x13682a45…18dc

0x34b655…2a6f

4 touches
1 conflict

0x178fe051…465a

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0xb72d9e4c…f2d1

0x34b655…2a6f

4 touches
1 conflict

0x00e21a9f…3583

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity