← previous blocknext block →recent activity

Analyzing

Block #75,502,325

12 transactions · 11 stateful · 2026-05-19 00:08:25 UTC

Parallelism

83/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,502,325  ·  12 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x1e65499b…df47

0x065c9d…c394

4 touches
1 conflict

0x8748b442…fd9e

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xfcb7b8b2…ebb3

0x065c9d…c394

4 touches
1 conflict

0xa66e9e80…ebd9

0x065c9d…c394

3 touches
1 conflict

0x7626b8a2…f221

0x065c9d…c394

3 touches
1 conflict

0x7c0b063d…e812

0x065c9d…c394

3 touches
1 conflict

0xf0b9cb45…e946

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

1 conflict on slot 0x1e65499b45…1ddf47

← previous block·next block →recent activity