← previous blocknext block →recent activity

Analyzing

Block #84,109,853

22 transactions · 18 stateful · 2026-06-27 21:06:01 UTC

Parallelism

77/100

Blocked

39%

Avg conflicts / tx

0.64

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,109,853  ·  22 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

0x90a9e3f8…17ab

0x34b655…2a6f

8 touches
6 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x2cae5ca4…9f80

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7db42404…3fe0

0x34b655…2a6f

4 touches
1 conflict

0x81c5483a…59e8

0x34b655…2a6f

4 touches
1 conflict

0x85b992ec…db0e

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

6 conflicts on slot 0x90a9e3f873…9117ab

← previous block·next block →recent activity