← previous blocknext block →recent activity

Analyzing

Block #97,362,272

23 transactions · 21 stateful · 2026-08-19 13:58:31 UTC

Parallelism

65/100

Blocked

48%

Avg conflicts / tx

1.48

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #97,362,272  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xbde524f4…43bf

0x34b655…2a6f

8 touches
6 conflicts

0xfb31d278…9107

0x34b655…2a6f

6 touches
3 conflicts

0x705ab4ae…0162

0x34b655…2a6f

6 touches
3 conflicts

0x45ef9175…5ab2

0x34b655…2a6f

6 touches
3 conflicts

0x6a26eb13…b01c

0x34b655…2a6f

6 touches
3 conflicts

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

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