← previous blocknext block →recent activity

Analyzing

Block #74,920,292

33 transactions · 22 stateful · 2026-05-16 07:14:43 UTC

Parallelism

76/100

Blocked

64%

Avg conflicts / tx

1.12

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,920,292  ·  33 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

0x66be8ad6…a2ad

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…001d

0x1b6862…e19c

6 touches
3 conflicts

0xc7f28b7a…5777

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…002d

0x1b6862…e19c

6 touches
3 conflicts

0xba5743c7…21c4

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

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

28 conflicts on slot 0x66be8ad622…91a2ad

← previous block·next block →recent activity