← previous blocknext block →recent activity

Analyzing

Block #83,651,965

28 transactions · 18 stateful · 2026-06-25 18:13:04 UTC

Parallelism

79/100

Blocked

39%

Avg conflicts / tx

0.39

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #83,651,965  ·  28 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

0x6ac6d1bf…8b19

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x1d351a9b…f2dd

0x34b655…2a6f

4 touches
1 conflict

0x2c75ca93…a569

0x34b655…2a6f

4 touches
1 conflict

0x3cf50d44…961b

0x34b655…2a6f

4 touches
1 conflict

0x3e776e71…4bbf

0x34b655…2a6f

4 touches
1 conflict

0x51049292…2704

0x34b655…2a6f

4 touches
1 conflict

0x705f195d…cc32

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: Perpl

3 conflicts on slot 0x6ac6d1bf0e…958b19

← previous block·next block →recent activity