← previous blocknext block →recent activity

Analyzing

Block #98,765,815

14 transactions · 13 stateful · 2026-08-24 13:08:14 UTC

Parallelism

79/100

Blocked

46%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,765,815  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

4 touches
1 conflict

0x1641b5fc…fa40

0x34b655…2a6f

4 touches
1 conflict

0x295780b7…d2d1

0x34b655…2a6f

4 touches
1 conflict

0x775dcec5…c10e

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0xc0a4133e…6110

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

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

1 conflict on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity