← previous blocknext block →recent activity

Analyzing

Block #84,615,008

24 transactions · 23 stateful · 2026-06-30 05:12:55 UTC

Parallelism

83/100

Blocked

30%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,615,008  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x40b5f387…a164

0x34b655…2a6f

8 touches
6 conflicts

0x7c0bdc54…9dde

0x34b655…2a6f

6 touches
3 conflicts

0xa457c06e…2f06

0x34b655…2a6f

6 touches
3 conflicts

0xb44d5376…33cc

0x34b655…2a6f

6 touches
3 conflicts

0xb9b4eff6…c3ef

0x34b655…2a6f

6 touches
3 conflicts

0xec0e0220…cb90

0x34b655…2a6f

6 touches
3 conflicts

0x1ca5aec6…c1e1

0x34b655…2a6f

6 touches
3 conflicts

0x24227bc5…cb16

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

6 conflicts on slot 0x40b5f38715…7ba164

← previous block·next block →recent activity