← previous blocknext block →recent activity

Analyzing

Block #98,431,518

21 transactions · 19 stateful · 2026-08-23 08:30:01 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

1.05

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,431,518  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x4ca87477…f8da

0xa6afd3…d132

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0x10d80fee…dbda

0x2b46c0…1669

6 touches
3 conflicts

0x40970e69…da50

0x2b46c0…1669

6 touches
3 conflicts

0x8cf3d245…1d0d

0x2b46c0…1669

6 touches
3 conflicts

0xb05cd4f5…73d0

0x2b46c0…1669

6 touches
3 conflicts

0xdb067026…9eb8

0x2b46c0…1669

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

15 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity