← previous blocknext block →recent activity

Analyzing

Block #76,232,563

21 transactions · 19 stateful · 2026-05-22 09:19:27 UTC

Parallelism

76/100

Blocked

37%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #76,232,563  ·  21 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

10 touches
10 conflicts

0x802741e7…56b9

0x34b655…2a6f

8 touches
6 conflicts

0x9fc6ea79…e2dc

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xdc54eb34…fe58

0x34b655…2a6f

6 touches
3 conflicts

0x4548467b…9058

0x34b655…2a6f

4 touches
1 conflict

0x537e2e5b…c3ab

0x34b655…2a6f

4 touches
1 conflict

0x9c0d6970…3dde

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

← previous block·next block →recent activity