← previous blocknext block →recent activity

Analyzing

Block #97,989,285

19 transactions · 19 stateful · 2026-08-21 19:23:46 UTC

Parallelism

68/100

Blocked

37%

Avg conflicts / tx

0.89

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #97,989,285  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xbd590df7…9891

0x34b655…2a6f

8 touches
6 conflicts

0xb0f5d668…99ac

0x34b655…2a6f

8 touches
6 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

8 touches
6 conflicts

0xfd4e632c…e14c

0x34b655…2a6f

8 touches
6 conflicts

0xf620f2c4…773e

0x34b655…2a6f

5 touches
3 conflicts

0x191cc704…89f4

0x34b655…2a6f

5 touches
3 conflicts

0x9c0f3849…3c10

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity