← previous blocknext block →recent activity

Analyzing

Block #92,960,885

16 transactions · 14 stateful · 2026-08-04 04:05:16 UTC

Parallelism

69/100

Blocked

50%

Avg conflicts / tx

0.69

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #92,960,885  ·  16 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

0xb3572c95…9c4a

0x2a68ba…90c5

4 touches
1 conflict

0x0271d9ac…9513

0x34b655…2a6f

4 touches
1 conflict

0x127480ab…144b

0x34b655…2a6f

4 touches
1 conflict

0x24b6091e…d294

0x34b655…2a6f

4 touches
1 conflict

0x3b9bb58c…e73a

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x6452fb9e…f8f1

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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

1 conflict on slot 0xb3572c958a…0d9c4a

← previous block·next block →recent activity