← previous blocknext block →recent activity

Analyzing

Block #94,857,478

15 transactions · 13 stateful · 2026-08-10 19:22:10 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #94,857,478  ·  15 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

4 touches
1 conflict

0x000bde1a…e123

0x34b655…2a6f

4 touches
1 conflict

0x04994ed2…9032

0x34b655…2a6f

4 touches
1 conflict

0x0b1afe68…20ad

0x34b655…2a6f

4 touches
1 conflict

0x1ea2b1f6…1d57

0x34b655…2a6f

4 touches
1 conflict

0x1ea2b1f6…1d58

0x34b655…2a6f

4 touches
1 conflict

0x2e095751…39dc

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

1 conflict on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity