← previous blocknext block →recent activity

Analyzing

Block #75,478,976

22 transactions · 14 stateful · 2026-05-18 21:28:11 UTC

Parallelism

82/100

Blocked

43%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,478,976  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xdacfd87d…dbdb

0xd32edf…ff58

7 touches
6 conflicts

0x66de0ce3…337a

0x188d58…ea8e

4 touches
1 conflict

0x66de0ce3…337b

0x188d58…ea8e

4 touches
1 conflict

0x846f2172…fd54

0x0555e3…2b9c

4 touches
1 conflict

0x00000000…0000

0x527211…b9f8

4 touches
1 conflict

0xa24d15eb…cc92

0x0555e3…2b9c

4 touches
1 conflict

0x00000000…000c

0x527211…b9f8

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

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

6 conflicts on slot 0xdacfd87d53…52dbdb

← previous block·next block →recent activity