← previous blocknext block →recent activity

Analyzing

Block #82,305,432

20 transactions · 18 stateful · 2026-06-19 12:16:48 UTC

Parallelism

60/100

Blocked

44%

Avg conflicts / tx

1.65

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #82,305,432  ·  20 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

16 touches
28 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x326a02b5…8dad

0x34b655…2a6f

8 touches
6 conflicts

0x6fbc2e5a…e69c

0x34b655…2a6f

8 touches
6 conflicts

0x97d5efed…1aa4

0x34b655…2a6f

6 touches
3 conflicts

0x9579025c…c3ec

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xb251976b…4938

0x34b655…2a6f

5 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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity