← previous blocknext block →recent activity

Analyzing

Block #75,523,971

16 transactions · 11 stateful · 2026-05-19 02:36:45 UTC

Parallelism

75/100

Blocked

27%

Avg conflicts / tx

0.31

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,523,971  ·  16 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

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xe32ade5c…a2a9

0xd32edf…ff58

5 touches
3 conflicts

0x44d7acbf…e67b

0x1b6862…e19c

4 touches
1 conflict

0xc8a8e1e2…f09b

0x065c9d…c394

4 touches
1 conflict

0x99a21305…dffc

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0xe75ce681…ba5f

0x188d58…ea8e

2 touches
0 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: 0x754704bc…afb603

3 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity