← previous blocknext block →recent activity

Analyzing

Block #97,370,100

20 transactions · 19 stateful · 2026-08-19 14:38:31 UTC

Parallelism

65/100

Blocked

58%

Avg conflicts / tx

1.5

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #97,370,100  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x482471ad…122f

0x34b655…2a6f

14 touches
21 conflicts

0x0bcbbcad…fc9c

0x34b655…2a6f

8 touches
6 conflicts

0x1b291796…f51f

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…002e

0x1b6862…e19c

4 touches
1 conflict

0xd996735f…8734

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

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

21 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity