← previous blocknext block →recent activity

Analyzing

Block #97,998,949

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

Parallelism

74/100

Blocked

39%

Avg conflicts / tx

0.53

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,998,949  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x279e3412…2a61

0x34b655…2a6f

4 touches
1 conflict

0x2d94ecd9…43db

0x34b655…2a6f

4 touches
1 conflict

0x3b5fbc7d…c8fe

0x34b655…2a6f

4 touches
1 conflict

0x3edf9996…0b7a

0x34b655…2a6f

4 touches
1 conflict

0x3fff7ccd…5a48

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 0xe5bb3628b5…71e5f1

← previous block·next block →recent activity