← previous blocknext block →recent activity

Analyzing

Block #99,242,029

27 transactions · 20 stateful · 2026-08-26 05:11:03 UTC

Parallelism

85/100

Blocked

35%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,242,029  ·  27 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

6 touches
3 conflicts

0x443a3e47…f4a4

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xbb97db90…4c93

0xc8689a…ee79

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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

3 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity