← previous blocknext block →recent activity

Analyzing

Block #75,084,981

15 transactions · 11 stateful · 2026-05-17 01:35:35 UTC

Parallelism

87/100

Blocked

36%

Avg conflicts / tx

0.33

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,084,981  ·  15 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

0xef17b8cd…9511

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x1364ed42…6866

0x065c9d…c394

4 touches
1 conflict

0x348fda08…7e96

0x065c9d…c394

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xb9868b52…c77f

0x34b655…2a6f

4 touches
1 conflict

0x14347d5f…edec

0x065c9d…c394

3 touches
1 conflict

0x3b84556a…8301

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

1 conflict on slot 0xef17b8cd5c…709511

← previous block·next block →recent activity