← previous blocknext block →recent activity

Analyzing

Block #97,825,376

25 transactions · 22 stateful · 2026-08-21 05:26:28 UTC

Parallelism

88/100

Blocked

27%

Avg conflicts / tx

0.32

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #97,825,376  ·  25 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

0xe22c1d6f…b574

0x77d53b…8080

4 touches
1 conflict

0x78e3ec57…8bf9

0x34b655…2a6f

4 touches
1 conflict

0x921893c3…b9b6

0x34b655…2a6f

4 touches
1 conflict

0xaaa40a27…27cd

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64db

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5e8

0x34b655…2a6f

4 touches
1 conflict

0xec7d120d…7084

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: 0x77d53b3b…378080

1 conflict on slot 0xe22c1d6f16…97b574

← previous block·next block →recent activity