← previous blocknext block →recent activity

Analyzing

Block #97,818,644

19 transactions · 19 stateful · 2026-08-21 04:52:26 UTC

Parallelism

74/100

Blocked

42%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,818,644  ·  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

0xaaa40a27…27cd

0x34b655…2a6f

8 touches
6 conflicts

0x6ea0c316…5341

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x921893c3…b9b6

0x34b655…2a6f

6 touches
3 conflicts

0xb81a6956…f7ca

0xa6afd3…d132

4 touches
1 conflict

0x6762cac2…3fb0

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64db

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

6 conflicts on slot 0xaaa40a275b…7727cd

← previous block·next block →recent activity