← previous blocknext block →recent activity

Analyzing

Block #75,196,559

9 transactions · 8 stateful · 2026-05-17 14:00:22 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,196,559  ·  9 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

0x4aa4f53b…899f

0x188d58…ea8e

4 touches
1 conflict

0x4aa4f53b…89a0

0x188d58…ea8e

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

0x45db0f10…6969

0x065c9d…c394

2 touches
0 conflicts

0x6b3d4202…a99c

0x065c9d…c394

2 touches
0 conflicts

0xac8b4bce…8ca6

0x065c9d…c394

2 touches
0 conflicts

0xba38536d…2b7d

0x065c9d…c394

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: 0x188d586d…f9ea8e

1 conflict on slot 0x4aa4f53bc4…b2899f

← previous block·next block →recent activity