← previous blocknext block →recent activity

Analyzing

Block #75,846,020

30 transactions · 17 stateful · 2026-05-20 14:24:01 UTC

Parallelism

73/100

Blocked

59%

Avg conflicts / tx

0.9

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,846,020  ·  30 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xba5743c7…21c6

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xeb0915f1…c150

0x34b655…2a6f

6 touches
3 conflicts

0x22f4d059…b7f4

0xd32edf…ff58

5 touches
3 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

4 touches
1 conflict

0x9d34b099…ff86

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

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity