← previous blocknext block →recent activity

Analyzing

Block #75,733,020

18 transactions · 15 stateful · 2026-05-20 01:50:40 UTC

Parallelism

72/100

Blocked

60%

Avg conflicts / tx

1.06

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,733,020  ·  18 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

0xb7b446d2…2006

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x700fa833…0498

0xd32edf…ff58

7 touches
6 conflicts

0xba5743c7…21c4

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xc166a323…1f33

0x34b655…2a6f

6 touches
3 conflicts

0x1c913164…5c2e

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

10 conflicts on slot 0xb7b446d20b…4f2006

← previous block·next block →recent activity