← previous blocknext block →recent activity

Analyzing

Block #98,664,649

27 transactions · 25 stateful · 2026-08-24 04:33:27 UTC

Parallelism

59/100

Blocked

56%

Avg conflicts / tx

1.63

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #98,664,649  ·  27 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

0x889d5e90…929a

0x2a68ba…90c5

14 touches
21 conflicts

0xa1087a5c…66c4

0x754704…b603

12 touches
15 conflicts

0x11b69a7e…334e

0xee8c0e…1242

12 touches
15 conflicts

0xf6f1c061…f9f9

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0018

0x1b6862…e19c

8 touches
6 conflicts

0xe545e668…4dc9

0xa6afd3…d132

8 touches
6 conflicts

0xba5743c7…21bf

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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: Kuru Exchange: MarginAccount

21 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity