← previous blocknext block →recent activity

Analyzing

Block #98,551,788

33 transactions · 23 stateful · 2026-08-23 18:45:17 UTC

Parallelism

88/100

Blocked

22%

Avg conflicts / tx

0.36

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,551,788  ·  33 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xa78c09f6…d069

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb85

0x1b6862…e19c

4 touches
1 conflict

0xb519624c…e716

0x754704…b603

4 touches
1 conflict

0xd98b3c10…67b8

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

6 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity