← previous blocknext block →recent activity

Analyzing

Block #98,730,994

21 transactions · 19 stateful · 2026-08-24 10:12:55 UTC

Parallelism

76/100

Blocked

37%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,730,994  ·  21 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

0x6518075e…2b17

0x2a68ba…90c5

10 touches
10 conflicts

0x930a64cc…8f78

0x40c49f…2af0

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x2b54cadb…4425

0xd18b7e…414b

10 touches
10 conflicts

0xec2a8d79…70cb

0x34b655…2a6f

6 touches
3 conflicts

0x7b41d5cd…00e6

0x34b655…2a6f

6 touches
3 conflicts

0xbec23443…9293

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

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 0x6518075e89…5f2b17

← previous block·next block →recent activity