← previous blocknext block →recent activity

Analyzing

Block #98,998,941

36 transactions · 35 stateful · 2026-08-25 08:41:35 UTC

Parallelism

61/100

Blocked

71%

Avg conflicts / tx

2.61

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #98,998,941  ·  36 txs across 14 waves  ·  depth 14
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

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

18 touches
36 conflicts

0xc31be29c…bdfd

0xd32edf…ff58

11 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x889d5e90…929a

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…002e

0x1b6862…e19c

8 touches
6 conflicts

0xc6a8c250…737f

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 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

36 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity