← previous blocknext block →recent activity

Analyzing

Block #75,478,951

35 transactions · 22 stateful · 2026-05-18 21:28:00 UTC

Parallelism

74/100

Blocked

64%

Avg conflicts / tx

1.43

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #75,478,951  ·  35 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

0x9b312780…2456

0xd32edf…ff58

13 touches
21 conflicts

0x17606ba6…1b6e

0x754704…b603

12 touches
15 conflicts

0x46cb45de…a566

0x188d58…ea8e

10 touches
10 conflicts

0x846f2172…fd54

0x0555e3…2b9c

10 touches
10 conflicts

0x46cb45de…a567

0x188d58…ea8e

8 touches
6 conflicts

0x00000000…0004

0xca50b9…1d03

6 touches
3 conflicts

0x6320bc8e…f9a3

0xd18b7e…414b

6 touches
3 conflicts

0x774ad574…3e75

0xd18b7e…414b

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

21 conflicts on slot 0x9b31278006…822456

← previous block·next block →recent activity