← previous blocknext block →recent activity

Analyzing

Block #99,082,591

25 transactions · 19 stateful · 2026-08-25 15:48:39 UTC

Parallelism

76/100

Blocked

42%

Avg conflicts / tx

0.64

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #99,082,591  ·  25 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

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x38b5b2ce…c5bb

0xfa32f9…f3f0

4 touches
1 conflict

0x99f666e3…b2a2

0x3bd359…433a

4 touches
1 conflict

0x9194f4a3…10b8

0x754704…b603

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x3494b9e5…682b

0x851145…3f07

4 touches
1 conflict

0x48cf4743…bfe1

0x851145…3f07

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

10 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity