← previous blocknext block →recent activity

Analyzing

Block #82,022,539

24 transactions · 23 stateful · 2026-06-18 04:50:17 UTC

Parallelism

67/100

Blocked

43%

Avg conflicts / tx

1.46

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #82,022,539  ·  24 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

16 touches
28 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x26470289…bb21

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002b

0x1b6862…e19c

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

28 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity