← previous blocknext block →recent activity

Analyzing

Block #75,233,022

8 transactions · 7 stateful · 2026-05-17 18:03:52 UTC

Parallelism

63/100

Blocked

43%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,233,022  ·  8 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

0x93af5ad2…45f1

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5e0fbadc…b3ab

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x20ac0567…c954

0x34b655…2a6f

2 touches
0 conflicts

0x2484cc15…5afc

0x34b655…2a6f

2 touches
0 conflicts

0x27d5dcb4…9dec

0x34b655…2a6f

2 touches
0 conflicts

0x3bb07d5e…582e

0x34b655…2a6f

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 0x93af5ad221…ad45f1

← previous block·next block →recent activity