← previous blocknext block →recent activity

Analyzing

Block #75,502,220

22 transactions · 13 stateful · 2026-05-19 00:07:43 UTC

Parallelism

82/100

Blocked

54%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,502,220  ·  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

0xef7fe2c4…99c7

0xd32edf…ff58

7 touches
6 conflicts

0x3a9149df…72e0

0x34b655…2a6f

6 touches
3 conflicts

0x3952b40f…4c8c

0x34b655…2a6f

6 touches
3 conflicts

0x15698ac9…2a46

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21bf

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

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 0xef7fe2c4c0…fc99c7

← previous block·next block →recent activity