← previous blocknext block →recent activity

Analyzing

Block #81,633,636

18 transactions · 16 stateful · 2026-06-16 09:36:33 UTC

Parallelism

72/100

Blocked

44%

Avg conflicts / tx

0.39

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #81,633,636  ·  18 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

0x557cd4fa…228c

0x2a68ba…90c5

4 touches
1 conflict

0xa472d565…9fe4

0x3bd359…433a

4 touches
1 conflict

0xa10c86f8…4b74

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x019883…2a9a

4 touches
1 conflict

0x00000000…0002

0x019883…2a9a

4 touches
1 conflict

0x00000000…0003

0x019883…2a9a

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0e3f9c0d…8a5f

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

← previous block·next block →recent activity