← previous blocknext block →recent activity

Analyzing

Block #75,732,984

33 transactions · 27 stateful · 2026-05-20 01:50:26 UTC

Parallelism

70/100

Blocked

59%

Avg conflicts / tx

1.18

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #75,732,984  ·  33 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x7151b1ad…4520

0x34b655…2a6f

8 touches
6 conflicts

0xd57b570b…3261

0xd32edf…ff58

7 touches
6 conflicts

0x14af78bb…aedb

0x1b6862…e19c

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

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: 0x34b6552d…112a6f

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity