← previous blocknext block →recent activity

Analyzing

Block #75,196,135

11 transactions · 11 stateful · 2026-05-17 13:57:31 UTC

Parallelism

73/100

Blocked

45%

Avg conflicts / tx

0.64

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,196,135  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xf3d7a307…4d63

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x003494c5…cd5c

0x065c9d…c394

4 touches
1 conflict

0xea57afd0…4232

0x34b655…2a6f

4 touches
1 conflict

0xba38536d…2b7d

0x065c9d…c394

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x8f6d4bd6…4e51

0x34b655…2a6f

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: 0x065c9d28…a9c394

3 conflicts on slot 0xf3d7a307cc…f14d63

← previous block·next block →recent activity