← previous blocknext block →recent activity

Analyzing

Block #97,371,072

24 transactions · 24 stateful · 2026-08-19 14:43:31 UTC

Parallelism

63/100

Blocked

50%

Avg conflicts / tx

1.79

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #97,371,072  ·  24 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

0x7e5ea60a…c4aa

0x34b655…2a6f

12 touches
15 conflicts

0xec7fe04a…3c56

0x34b655…2a6f

12 touches
15 conflicts

0x92385428…6941

0x34b655…2a6f

10 touches
10 conflicts

0xec7d120d…7084

0x34b655…2a6f

8 touches
6 conflicts

0xf729d00d…25d5

0x34b655…2a6f

6 touches
3 conflicts

0x4360b49f…140d

0x34b655…2a6f

6 touches
3 conflicts

0x886db264…846e

0x34b655…2a6f

6 touches
3 conflicts

0xc788862c…c259

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

15 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity