← previous blocknext block →recent activity

Analyzing

Block #75,097,823

14 transactions · 11 stateful · 2026-05-17 03:01:12 UTC

Parallelism

71/100

Blocked

27%

Avg conflicts / tx

0.21

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,097,823  ·  14 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

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x6eba5e7f…4b52

0x34b655…2a6f

4 touches
1 conflict

0x7b97d40a…09ed

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xfefd1e1d…5fed

0x34b655…2a6f

4 touches
1 conflict

0x18978822…2623

0x34b655…2a6f

4 touches
1 conflict

0x57b1d09f…1dfa

0x065c9d…c394

2 touches
0 conflicts

0x33018431…8f5c

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: 0x34b6552d…112a6f

1 conflict on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity