← previous blocknext block →recent activity

Analyzing

Block #83,623,763

22 transactions · 19 stateful · 2026-06-25 15:04:41 UTC

Parallelism

68/100

Blocked

42%

Avg conflicts / tx

0.82

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #83,623,763  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xe99d8e68…a16e

0x34b655…2a6f

10 touches
10 conflicts

0xa47c4f55…84b4

0x34b655…2a6f

6 touches
3 conflicts

0x849cf3bb…e115

0x34b655…2a6f

6 touches
3 conflicts

0xd6d4eb00…30f3

0x34b655…2a6f

6 touches
3 conflicts

0x022f72c3…07b6

0xc8689a…ee79

6 touches
3 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

6 touches
3 conflicts

0xfd4e2262…cd8c

0x34b655…2a6f

6 touches
3 conflicts

0x967b4a40…7a78

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

10 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity