← previous blocknext block →recent activity

Analyzing

Block #99,356,291

25 transactions · 21 stateful · 2026-08-26 14:45:59 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.4

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,356,291  ·  25 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x27b6010e…e4aa

0x34b655…2a6f

6 touches
3 conflicts

0x8f49ed65…2016

0x40c49f…2af0

4 touches
1 conflict

0xd68f9655…0502

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x065ff70b…356d

0x40c49f…2af0

4 touches
1 conflict

0x1ff88a42…51ee

0x40c49f…2af0

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