← previous blocknext block →recent activity

Analyzing

Block #84,330,921

17 transactions · 15 stateful · 2026-06-28 21:38:28 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,330,921  ·  17 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xcde75077…ccee

0x34b655…2a6f

6 touches
3 conflicts

0x00e21a9f…3583

0x34b655…2a6f

4 touches
1 conflict

0x0d2e1791…c1dd

0x34b655…2a6f

4 touches
1 conflict

0x206f4379…e08a

0x34b655…2a6f

4 touches
1 conflict

0x32409e80…a396

0x34b655…2a6f

4 touches
1 conflict

0x4bdaea9a…1e71

0x34b655…2a6f

4 touches
1 conflict

0x53baa009…68b3

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity