← previous blocknext block →recent activity

Analyzing

Block #83,655,427

18 transactions · 16 stateful · 2026-06-25 18:36:06 UTC

Parallelism

61/100

Blocked

56%

Avg conflicts / tx

1.22

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #83,655,427  ·  18 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

12 touches
15 conflicts

0x1c48b3ac…a03c

0x34b655…2a6f

8 touches
6 conflicts

0xc0b9bd73…7f1c

0x34b655…2a6f

6 touches
3 conflicts

0xd064a456…b881

0x34b655…2a6f

6 touches
3 conflicts

0x022f72c3…07b6

0xc8689a…ee79

6 touches
3 conflicts

0xe46a9e83…22b5

0x34b655…2a6f

6 touches
3 conflicts

0x487922c6…dbd2

0x34b655…2a6f

6 touches
3 conflicts

0x75291f8b…3ac0

0x34b655…2a6f

4 touches
1 conflict

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 0xe99d8e683a…2ea16e

← previous block·next block →recent activity