← previous blocknext block →recent activity

Analyzing

Block #98,015,227

24 transactions · 16 stateful · 2026-08-21 21:34:40 UTC

Parallelism

88/100

Blocked

38%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,015,227  ·  24 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd6bd849a…5597

0x2a68ba…90c5

6 touches
3 conflicts

0x40970e69…da50

0x2b46c0…1669

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x5b09bf44…5907

0xa6afd3…d132

6 touches
3 conflicts

0x6d8ad688…4bf5

0xa6afd3…d132

6 touches
3 conflicts

0x8cf3d245…1d0d

0x2b46c0…1669

6 touches
3 conflicts

0xb5c4826d…bdd6

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

3 conflicts on slot 0xd6bd849ae7…7c5597

← previous block·next block →recent activity