← previous blocknext block →recent activity

Analyzing

Block #83,641,834

26 transactions · 19 stateful · 2026-06-25 17:05:25 UTC

Parallelism

85/100

Blocked

37%

Avg conflicts / tx

0.54

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,641,834  ·  26 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x9ff886f2…8f4c

0x34b655…2a6f

8 touches
6 conflicts

0x1b1df992…40eb

0x34b655…2a6f

8 touches
6 conflicts

0xb1c67a7d…b9b1

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xaa7ee7…f0e4

6 touches
3 conflicts

0x022f72c3…07b6

0xc8689a…ee79

6 touches
3 conflicts

0x7e6c970a…65af

0x34b655…2a6f

6 touches
3 conflicts

0x8e5cc690…b06b

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

6 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity