← previous blocknext block →recent activity

Analyzing

Block #99,199,314

23 transactions · 20 stateful · 2026-08-26 01:36:08 UTC

Parallelism

83/100

Blocked

30%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,199,314  ·  23 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

0xfe45073e…6315

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xfc8d572c…b27d

0x34b655…2a6f

4 touches
1 conflict

0x11258774…9892

0x2a68ba…90c5

4 touches
1 conflict

0x1aad705d…35d2

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

3 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity