← previous blocknext block →recent activity

Analyzing

Block #75,116,832

11 transactions · 11 stateful · 2026-05-17 05:08:09 UTC

Parallelism

73/100

Blocked

36%

Avg conflicts / tx

0.55

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,116,832  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00bac013…a28c

0x91b81b…6d56

6 touches
3 conflicts

0x3e49348b…9445

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xc7f28b7a…5777

0x34b655…2a6f

6 touches
3 conflicts

0xc079cc93…b57b

0xea1b8e…c5ec

4 touches
1 conflict

0x1c1e24b9…99d8

0x34b655…2a6f

4 touches
1 conflict

0xaa0d0542…d8ec

0x34b655…2a6f

4 touches
1 conflict

0xc6939b20…31cd

0x34b655…2a6f

4 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: 0x91b81bfb…8e6d56

3 conflicts on slot 0x00bac0131a…bba28c

← previous block·next block →recent activity