← previous blocknext block →recent activity

Analyzing

Block #98,755,778

22 transactions · 21 stateful · 2026-08-24 12:17:42 UTC

Parallelism

73/100

Blocked

38%

Avg conflicts / tx

0.82

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,755,778  ·  22 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

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0xd1cdecc3…ada6

0x065c9d…c394

7 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf106d229…efb1

0x065c9d…c394

3 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