← previous blocknext block →recent activity

Analyzing

Block #82,966,920

27 transactions · 23 stateful · 2026-06-22 13:56:05 UTC

Parallelism

89/100

Blocked

26%

Avg conflicts / tx

0.26

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #82,966,920  ·  27 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

0x557cd4fa…228c

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x2965e2d6…5800

0x34b655…2a6f

4 touches
1 conflict

0xc9eaeefd…d5a3

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x4cd75b0d…ddb4

0x40c49f…2af0

4 touches
1 conflict

0xc5d7e85d…b578

0x40c49f…2af0

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 0x557cd4fad5…e4228c

← previous block·next block →recent activity