← previous blocknext block →recent activity

Analyzing

Block #93,346,542

23 transactions · 18 stateful · 2026-08-05 12:26:03 UTC

Parallelism

74/100

Blocked

50%

Avg conflicts / tx

0.61

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #93,346,542  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x80afd9d9…57cf

0x065c9d…c394

6 touches
3 conflicts

0xb4e0a934…5fc7

0x34b655…2a6f

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0x0ac67576…1cc5

0x34b655…2a6f

4 touches
1 conflict

0x27279e7f…b1e6

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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