← previous blocknext block →recent activity

Analyzing

Block #83,626,046

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

Parallelism

64/100

Blocked

45%

Avg conflicts / tx

1.08

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #83,626,046  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xe155a04c…f267

0x34b655…2a6f

12 touches
15 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

12 touches
15 conflicts

0x022f72c3…07b6

0xc8689a…ee79

10 touches
10 conflicts

0x9fbabe09…8dd6

0x34b655…2a6f

10 touches
10 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

10 touches
10 conflicts

0x16639a37…f836

0x34b655…2a6f

6 touches
3 conflicts

0x055139c8…f6d4

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

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

15 conflicts on slot 0xe155a04cc1…f3f267

← previous block·next block →recent activity