← previous blocknext block →recent activity

Analyzing

Block #75,502,283

12 transactions · 11 stateful · 2026-05-19 00:08:08 UTC

Parallelism

75/100

Blocked

36%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,502,283  ·  12 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

0x15698ac9…2a46

0x34b655…2a6f

6 touches
3 conflicts

0x51e6835b…f157

0xd32edf…ff58

5 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x101025e1…e017

0x065c9d…c394

2 touches
0 conflicts

0x256fa6cf…c0e1

0x065c9d…c394

2 touches
0 conflicts

0x3be3244a…49e1

0x065c9d…c394

2 touches
0 conflicts

0x3d7afa4f…1c7c

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

3 conflicts on slot 0x15698ac9db…df2a46

← previous block·next block →recent activity