← previous blocknext block →recent activity

Analyzing

Block #83,494,772

21 transactions · 18 stateful · 2026-06-25 00:43:58 UTC

Parallelism

76/100

Blocked

44%

Avg conflicts / tx

0.81

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,494,772  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0xf5310ef7…485a

0x40c49f…2af0

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x1ee4a6d2…6389

0x34b655…2a6f

4 touches
1 conflict

0x8d6cfd93…6eb6

0x34b655…2a6f

4 touches
1 conflict

0x8e5cc690…b06b

0x34b655…2a6f

4 touches
1 conflict

0x9fbabe09…8dd6

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

10 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity