← previous blocknext block →recent activity

Analyzing

Block #99,182,149

31 transactions · 21 stateful · 2026-08-26 00:09:45 UTC

Parallelism

71/100

Blocked

52%

Avg conflicts / tx

1.13

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #99,182,149  ·  31 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

14 touches
21 conflicts

0xa1087a5c…66c4

0x754704…b603

14 touches
21 conflicts

0xc80e9211…84ef

0x065c9d…c394

12 touches
15 conflicts

0x11258774…9892

0x2a68ba…90c5

4 touches
1 conflict

0xa5abd8a9…4328

0x065c9d…c394

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5b842fa7…badd

0x3bd359…433a

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

21 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity