← previous blocknext block →recent activity

Analyzing

Block #75,097,055

11 transactions · 11 stateful · 2026-05-17 02:56:05 UTC

Parallelism

73/100

Blocked

27%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0x7cee1be1…e770

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xfa2527aa…9dd5

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0006

0x2ab50b…5c41

2 touches
0 conflicts

0x006a9d46…6d59

0x2ab50b…5c41

2 touches
0 conflicts

0x0253652f…1607

0x2ab50b…5c41

2 touches
0 conflicts

0x05b8ccbb…46bc

0x2ab50b…5c41

2 touches
0 conflicts

0x0bdddc5f…d555

0x2ab50b…5c41

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 0x7cee1be1f4…b4e770

← previous block·next block →recent activity