← previous blocknext block →recent activity

Analyzing

Block #94,221,267

17 transactions · 17 stateful · 2026-08-08 13:48:45 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.88

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,221,267  ·  17 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

8 touches
6 conflicts

0xfac29b89…03a7

0x065c9d…c394

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x0778475b…bd75

0x2a68ba…90c5

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x595233b5…c4aa

0x754704…b603

4 touches
1 conflict

0x66bdb4c2…7ea6

0x34b655…2a6f

4 touches
1 conflict

0x8299fe6c…5752

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

6 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity