← previous blocknext block →recent activity

Analyzing

Block #82,023,032

24 transactions · 19 stateful · 2026-06-18 04:53:34 UTC

Parallelism

67/100

Blocked

42%

Avg conflicts / tx

1.04

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #82,023,032  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x217bd767…b79e

0x34b655…2a6f

6 touches
3 conflicts

0x4fe95978…4ea7

0x34b655…2a6f

6 touches
3 conflicts

0xa51de3df…c65a

0x34b655…2a6f

6 touches
3 conflicts

0xc4f9dc2c…f781

0x34b655…2a6f

6 touches
3 conflicts

0xd653c5b0…a35a

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity