← previous blocknext block →recent activity

Analyzing

Block #99,079,968

27 transactions · 18 stateful · 2026-08-25 15:35:24 UTC

Parallelism

74/100

Blocked

50%

Avg conflicts / tx

0.81

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #99,079,968  ·  27 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd08db6ee…a943

0x40c49f…2af0

8 touches
6 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0x00000000…0002

0xf5b5f7…6d70

6 touches
3 conflicts

0xd1203697…1ae0

0x40c49f…2af0

6 touches
3 conflicts

0xd3dfe4b8…9482

0x40c49f…2af0

5 touches
3 conflicts

0x3a921be0…779c

0x2a68ba…90c5

4 touches
1 conflict

0x7f4a8466…f2cc

0x2b46c0…1669

4 touches
1 conflict

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