← previous blocknext block →recent activity

Analyzing

Block #83,637,205

29 transactions · 28 stateful · 2026-06-25 16:34:31 UTC

Parallelism

76/100

Blocked

50%

Avg conflicts / tx

1.38

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #83,637,205  ·  29 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

0x00000000…0002

0xaa7ee7…f0e4

14 touches
21 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0xda7f9bd2…e332

0x34b655…2a6f

10 touches
10 conflicts

0xec0e0220…cb90

0x34b655…2a6f

6 touches
3 conflicts

0x39fa7a0d…33a4

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x75cdffd8…c217

0x34b655…2a6f

6 touches
3 conflicts

0xe99d8e68…a16e

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: 0xaa7ee7ce…aff0e4

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity