← previous blocknext block →recent activity

Analyzing

Block #97,898,954

34 transactions · 25 stateful · 2026-08-21 11:44:16 UTC

Parallelism

74/100

Blocked

36%

Avg conflicts / tx

0.91

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #97,898,954  ·  34 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

0x482471ad…122f

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xbde524f4…43bf

0x34b655…2a6f

12 touches
15 conflicts

0x705ab4ae…0162

0x34b655…2a6f

7 touches
6 conflicts

0x76e2c80e…1811

0x34b655…2a6f

6 touches
3 conflicts

0x4f6fc25c…1d50

0x34b655…2a6f

5 touches
3 conflicts

0x9182cdc8…e2e5

0x34b655…2a6f

5 touches
3 conflicts

0x2c2db8e9…fdc7

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

21 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity