← previous blocknext block →recent activity

Analyzing

Block #82,970,726

19 transactions · 17 stateful · 2026-06-22 14:21:32 UTC

Parallelism

68/100

Blocked

47%

Avg conflicts / tx

1.11

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #82,970,726  ·  19 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

0x4fe95978…4ea7

0x34b655…2a6f

6 touches
3 conflicts

0x548145a9…cfce

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x006c3b86…59a9

0x34b655…2a6f

5 touches
3 conflicts

0x11431f9d…42c5

0x34b655…2a6f

4 touches
1 conflict

0x157dbfb2…4089

0x34b655…2a6f

4 touches
1 conflict

0xb9b4eff6…c3ef

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

15 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity