← previous blocknext block →recent activity

Analyzing

Block #84,031,108

23 transactions · 17 stateful · 2026-06-27 12:21:18 UTC

Parallelism

74/100

Blocked

53%

Avg conflicts / tx

0.65

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #84,031,108  ·  23 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

0xd026fe03…7748

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x42341814…60f1

0x34b655…2a6f

5 touches
3 conflicts

0x73339976…42a3

0xd32edf…ff58

5 touches
3 conflicts

0x9966da31…0d0f

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f0

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

3 conflicts on slot 0xd026fe0331…887748

← previous block·next block →recent activity