← previous blocknext block →recent activity

Analyzing

Block #82,293,363

25 transactions · 22 stateful · 2026-06-19 10:56:29 UTC

Parallelism

72/100

Blocked

41%

Avg conflicts / tx

1.16

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #82,293,363  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0x3e1c3586…83d7

0xa6afd3…d132

8 touches
6 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xffa7d0a4…b10a

0x40c49f…2af0

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x9cc13b7b…c0ac

0xa6afd3…d132

4 touches
1 conflict

0x5581d709…ab77

0x2a68ba…90c5

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

21 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity