← previous blocknext block →recent activity

Analyzing

Block #98,734,013

29 transactions · 25 stateful · 2026-08-24 10:28:07 UTC

Parallelism

66/100

Blocked

48%

Avg conflicts / tx

1.14

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #98,734,013  ·  29 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x002fed35…79fa

0x2a68ba…90c5

14 touches
21 conflicts

0x2b54cadb…4425

0xd18b7e…414b

12 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

12 touches
15 conflicts

0x25453842…8d61

0x40c49f…2af0

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x5a548af5…0eb0

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

21 conflicts on slot 0x002fed350f…7379fa

← previous block·next block →recent activity