← previous blocknext block →recent activity

Analyzing

Block #98,736,230

23 transactions · 22 stateful · 2026-08-24 10:39:16 UTC

Parallelism

65/100

Blocked

41%

Avg conflicts / tx

1.09

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #98,736,230  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x6518075e…2b17

0x2a68ba…90c5

14 touches
21 conflicts

0x18430837…cc00

0x40c49f…2af0

12 touches
15 conflicts

0x2b54cadb…4425

0xd18b7e…414b

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x3f81bcfb…2905

0x40c49f…2af0

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x22e0cc1d…ad04

0x34b655…2a6f

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

21 conflicts on slot 0x6518075e89…5f2b17

← previous block·next block →recent activity