← previous blocknext block →recent activity

Analyzing

Block #97,990,311

20 transactions · 17 stateful · 2026-08-21 19:28:57 UTC

Parallelism

70/100

Blocked

47%

Avg conflicts / tx

0.8

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #97,990,311  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xbfcf3203…568d

0x40c49f…2af0

4 touches
1 conflict

0x2130a548…c1de

0x34b655…2a6f

4 touches
1 conflict

0x759871b5…8eaa

0x34b655…2a6f

4 touches
1 conflict

0xcaa5e459…c7eb

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x065ff70b…356d

0x40c49f…2af0

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

10 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity