← previous blocknext block →recent activity

Analyzing

Block #97,370,092

24 transactions · 23 stateful · 2026-08-19 14:38:29 UTC

Parallelism

58/100

Blocked

52%

Avg conflicts / tx

1.54

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #97,370,092  ·  24 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xc788862c…c259

0x34b655…2a6f

14 touches
21 conflicts

0x0bcbbcad…fc9c

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0x7f2a62b8…77c8

0x34b655…2a6f

6 touches
3 conflicts

0xd66696e0…0842

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 0xc788862c2e…6ec259

← previous block·next block →recent activity