← previous blocknext block →recent activity

Analyzing

Block #98,773,582

52 transactions · 43 stateful · 2026-08-24 13:47:19 UTC

Parallelism

83/100

Blocked

72%

Avg conflicts / tx

1.38

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #98,773,582  ·  52 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

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0x889d5e90…929a

0x2a68ba…90c5

12 touches
15 conflicts

0x784d04bf…cd0d

0xd32edf…ff58

11 touches
15 conflicts

0x065ff70b…356d

0x40c49f…2af0

8 touches
6 conflicts

0x00000000…0002

0xbb3f3c…e046

8 touches
6 conflicts

0x84611dd3…b343

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xd6bd849a…5597

0x2a68ba…90c5

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

15 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity