← previous blocknext block →recent activity

Analyzing

Block #75,196,777

32 transactions · 27 stateful · 2026-05-17 14:01:51 UTC

Parallelism

75/100

Blocked

70%

Avg conflicts / tx

1.63

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,196,777  ·  32 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

0x9e7794db…792c

0xd32edf…ff58

15 touches
28 conflicts

0x3e49348b…9445

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0xba5743c7…21c1

0x1b6862…e19c

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 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 0x9e7794db2f…9b792c

← previous block·next block →recent activity