← previous blocknext block →recent activity

Analyzing

Block #97,990,717

23 transactions · 20 stateful · 2026-08-21 19:31:02 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,990,717  ·  23 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

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0007

0x340143…768f

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x2e5cec44…05c6

0x065c9d…c394

4 touches
1 conflict

0x11258774…9892

0x2a68ba…90c5

4 touches
1 conflict

0x3bdd71a2…b6eb

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 0x326a02b5c5…5c8dad

← previous block·next block →recent activity