← previous blocknext block →recent activity

Analyzing

Block #81,479,062

18 transactions · 17 stateful · 2026-06-15 16:26:57 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

1.11

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #81,479,062  ·  18 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

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0xb4db7f29…cf1a

0x40c49f…2af0

4 touches
1 conflict

0x5581d709…ab77

0x2a68ba…90c5

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xb3572c95…9c4a

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x1d44909b…e905

0xa6afd3…d132

4 touches
1 conflict

0x00000000…003d

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

15 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity