← previous blocknext block →recent activity

Analyzing

Block #98,653,872

22 transactions · 22 stateful · 2026-08-24 03:37:07 UTC

Parallelism

68/100

Blocked

41%

Avg conflicts / tx

1.14

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #98,653,872  ·  22 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

0xd6bd849a…5597

0x2a68ba…90c5

14 touches
21 conflicts

0x11b69a7e…334e

0xee8c0e…1242

12 touches
15 conflicts

0x5a60001a…adf4

0xa6afd3…d132

12 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

12 touches
15 conflicts

0x00000000…001f

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002f

0x1b6862…e19c

6 touches
3 conflicts

0x11998eac…f9a6

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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

21 conflicts on slot 0xd6bd849ae7…7c5597

← previous block·next block →recent activity