← previous blocknext block →recent activity

Analyzing

Block #97,898,327

19 transactions · 17 stateful · 2026-08-21 11:41:05 UTC

Parallelism

84/100

Blocked

29%

Avg conflicts / tx

0.37

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #97,898,327  ·  19 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

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x074c08f8…fb56

0x34b655…2a6f

4 touches
1 conflict

0xb7b16dd0…0426

0x34b655…2a6f

4 touches
1 conflict

0xb63ef486…0dcc

0x34b655…2a6f

4 touches
1 conflict

0xadb553c0…430a

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

1 conflict on slot 0x7de579746e…f0f5ba

← previous block·next block →recent activity