← previous blocknext block →recent activity

Analyzing

Block #83,660,217

23 transactions · 23 stateful · 2026-06-25 19:08:02 UTC

Parallelism

61/100

Blocked

52%

Avg conflicts / tx

1.57

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #83,660,217  ·  23 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x79e62da8…efdc

0x34b655…2a6f

16 touches
28 conflicts

0x7ee6007b…fd68

0x34b655…2a6f

8 touches
6 conflicts

0x022f72c3…07b6

0xc8689a…ee79

8 touches
6 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0xfbf0b409…2ac6

0x34b655…2a6f

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xac61d3a4…7da8

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

28 conflicts on slot 0x79e62da89b…71efdc

← previous block·next block →recent activity