← previous blocknext block →recent activity

Analyzing

Block #75,732,976

39 transactions · 31 stateful · 2026-05-20 01:50:23 UTC

Parallelism

77/100

Blocked

58%

Avg conflicts / tx

1.38

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #75,732,976  ·  39 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x0777203a…8dda

0xd32edf…ff58

15 touches
28 conflicts

0x17606ba6…1b6e

0x754704…b603

12 touches
15 conflicts

0x00000000…001d

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb85

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x12e7c471…901c

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: 0xd32edf66…9fff58

28 conflicts on slot 0x0777203a87…af8dda

← previous block·next block →recent activity