← previous blocknext block →recent activity

Analyzing

Block #97,522,017

20 transactions · 19 stateful · 2026-08-20 03:45:56 UTC

Parallelism

55/100

Blocked

47%

Avg conflicts / tx

1.1

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #97,522,017  ·  20 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x1dc86774…166a

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0007

0xc1570a…c91b

4 touches
1 conflict

0x35c37635…11a6

0x34b655…2a6f

4 touches
1 conflict

0x3a06aac2…c200

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 0x1dc86774a8…36166a

← previous block·next block →recent activity