← previous blocknext block →recent activity

Analyzing

Block #98,749,358

28 transactions · 24 stateful · 2026-08-24 11:45:18 UTC

Parallelism

64/100

Blocked

58%

Avg conflicts / tx

1.54

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #98,749,358  ·  28 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

0xca841faa…486a

0x34b655…2a6f

16 touches
28 conflicts

0x171d9a84…b3b7

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x6f6fc26c…3e34

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0029

0x1b6862…e19c

6 touches
3 conflicts

0x2b093939…9084

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xf92e07d1…0c1e

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

28 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity