← previous blocknext block →recent activity

Analyzing

Block #83,654,689

22 transactions · 18 stateful · 2026-06-25 18:31:11 UTC

Parallelism

73/100

Blocked

44%

Avg conflicts / tx

0.82

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #83,654,689  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x2a513dfb…2bb8

0x34b655…2a6f

10 touches
10 conflicts

0xa0c6e179…a103

0x34b655…2a6f

6 touches
3 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x5bd818fc…4f86

0x34b655…2a6f

4 touches
1 conflict

0x6ac6d1bf…8b19

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 0x2a513dfb89…c02bb8

← previous block·next block →recent activity