← previous blocknext block →recent activity

Analyzing

Block #75,689,492

14 transactions · 11 stateful · 2026-05-19 21:01:00 UTC

Parallelism

86/100

Blocked

18%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,689,492  ·  14 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

0xcc4f1f14…aa5f

0x065c9d…c394

4 touches
1 conflict

0x99a21305…dffc

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x2ac79079…c1af

0x065c9d…c394

2 touches
0 conflicts

0x5f77d607…2c84

0x065c9d…c394

2 touches
0 conflicts

0x7d1b221e…001e

0x065c9d…c394

2 touches
0 conflicts

0xd025182e…30ea

0x065c9d…c394

2 touches
0 conflicts

0xf03ecf07…5f20

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

1 conflict on slot 0xcc4f1f1446…7caa5f

← previous block·next block →recent activity