← previous blocknext block →recent activity

Analyzing

Block #75,261,960

12 transactions · 9 stateful · 2026-05-17 21:17:22 UTC

Parallelism

75/100

Blocked

33%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,261,960  ·  12 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

0xfe2bac2b…2cec

0x065c9d…c394

6 touches
3 conflicts

0x4bc9c83a…663c

0x065c9d…c394

4 touches
1 conflict

0x737c2611…5794

0x065c9d…c394

3 touches
1 conflict

0x06f1299b…f25a

0x065c9d…c394

3 touches
1 conflict

0xa957aeb2…0c79

0x065c9d…c394

3 touches
1 conflict

0x2bcc8be0…e9f3

0x065c9d…c394

3 touches
1 conflict

0x21fdea25…1396

0x065c9d…c394

3 touches
1 conflict

0xfa790d24…17be

0x065c9d…c394

3 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 0xfe2bac2b2f…482cec

← previous block·next block →recent activity