← previous blocknext block →recent activity

Analyzing

Block #98,327,507

28 transactions · 24 stateful · 2026-08-22 23:46:45 UTC

Parallelism

61/100

Blocked

54%

Avg conflicts / tx

1.64

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #98,327,507  ·  28 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

14 touches
21 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

10 touches
10 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x65ac83fa…4952

0x34b655…2a6f

8 touches
6 conflicts

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0x7aad02c6…b979

0x34b655…2a6f

8 touches
6 conflicts

0xfa324e43…8895

0x1b6862…e19c

6 touches
3 conflicts

0x315e07b8…9823

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity