← previous blocknext block →recent activity

Analyzing

Block #83,669,365

26 transactions · 18 stateful · 2026-06-25 20:09:03 UTC

Parallelism

69/100

Blocked

50%

Avg conflicts / tx

0.88

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #83,669,365  ·  26 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xbd68c7c7…40b3

0x34b655…2a6f

6 touches
3 conflicts

0xe20a9313…c20a

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x3e2c3d66…b580

0x34b655…2a6f

4 touches
1 conflict

0x6454462f…d327

0x34b655…2a6f

4 touches
1 conflict

0x65df2980…8edc

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

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