← previous blocknext block →recent activity

Analyzing

Block #75,502,254

27 transactions · 22 stateful · 2026-05-19 00:07:57 UTC

Parallelism

81/100

Blocked

64%

Avg conflicts / tx

1.07

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,502,254  ·  27 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x3d52db1e…623e

0xd32edf…ff58

9 touches
10 conflicts

0x15698ac9…2a46

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x99a21305…dffc

0x2a68ba…90c5

6 touches
3 conflicts

0x10d80fee…dbda

0x1d1325…2305

4 touches
1 conflict

0x3484c9df…bfd5

0x1d1325…2305

4 touches
1 conflict

0x8cf3d245…1d0d

0x1d1325…2305

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: 0xd32edf66…9fff58

10 conflicts on slot 0x3d52db1e96…4c623e

← previous block·next block →recent activity