← previous blocknext block →recent activity

Analyzing

Block #75,478,680

28 transactions · 15 stateful · 2026-05-18 21:26:10 UTC

Parallelism

82/100

Blocked

40%

Avg conflicts / tx

0.54

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,478,680  ·  28 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x0dbf9688…c6cf

0xd18b7e…414b

10 touches
10 conflicts

0x751db0c0…4f57

0xd18b7e…414b

8 touches
6 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

8 touches
6 conflicts

0x00000000…0004

0x614b85…a284

8 touches
6 conflicts

0x00000000…0000

0x614b85…a284

8 touches
6 conflicts

0x51ca3051…0972

0x3bd359…433a

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x846f2172…fd54

0x0555e3…2b9c

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: 0xd18b7ec5…10414b

10 conflicts on slot 0x0dbf9688de…b0c6cf

← previous block·next block →recent activity