← previous blocknext block →recent activity

Analyzing

Block #83,660,060

16 transactions · 15 stateful · 2026-06-25 19:06:59 UTC

Parallelism

63/100

Blocked

67%

Avg conflicts / tx

1.5

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #83,660,060  ·  16 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

0x925c118c…a1d8

0x34b655…2a6f

12 touches
15 conflicts

0x022f72c3…07b6

0xc8689a…ee79

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x7ee6007b…fd68

0x34b655…2a6f

8 touches
6 conflicts

0x9b58e20f…2dd9

0x34b655…2a6f

8 touches
6 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

8 touches
6 conflicts

0xf324b405…ca30

0x34b655…2a6f

8 touches
6 conflicts

0xfbf0b409…2ac6

0x34b655…2a6f

8 touches
6 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

15 conflicts on slot 0x925c118c7b…bea1d8

← previous block·next block →recent activity