← previous blocknext block →recent activity

Analyzing

Block #75,178,280

13 transactions · 13 stateful · 2026-05-17 11:58:22 UTC

Parallelism

77/100

Blocked

31%

Avg conflicts / tx

0.69

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,178,280  ·  13 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

0xfe2bac2b…2cec

0x065c9d…c394

6 touches
3 conflicts

0xea57afd0…4232

0x34b655…2a6f

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd031baf9…a968

0xd32edf…ff58

3 touches
1 conflict

0x235df5d9…5cde

0x065c9d…c394

3 touches
1 conflict

0x9194f4a3…10b8

0x754704…b603

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

3 conflicts on slot 0xf3d7a307cc…f14d63

← previous block·next block →recent activity