← previous blocknext block →recent activity

Analyzing

Block #97,363,999

21 transactions · 21 stateful · 2026-08-19 14:07:26 UTC

Parallelism

81/100

Blocked

29%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,363,999  ·  21 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

0x096a2f62…dc58

0x34b655…2a6f

6 touches
3 conflicts

0xfc3d5171…8357

0x34b655…2a6f

6 touches
3 conflicts

0x3ca268be…8865

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x48e3acd8…cf41

0x34b655…2a6f

4 touches
1 conflict

0x742436a7…c4d4

0x34b655…2a6f

4 touches
1 conflict

0x948836ff…59ab

0x34b655…2a6f

4 touches
1 conflict

0xa60eabc0…9f8c

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 0x096a2f626d…f7dc58

← previous block·next block →recent activity