← previous blocknext block →recent activity

Analyzing

Block #75,516,150

19 transactions · 6 stateful · 2026-05-19 01:43:11 UTC

Parallelism

89/100

Blocked

17%

Avg conflicts / tx

0.05

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,516,150  ·  19 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x97b0b2ee…4666

0x34b655…2a6f

4 touches
1 conflict

0x9e719c7a…df63

0x34b655…2a6f

4 touches
1 conflict

0xa92c8763…6d7f

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x3484c9df…bfd5

0x1d1325…2305

2 touches
0 conflicts

0x8cf3d245…1d0d

0x1d1325…2305

2 touches
0 conflicts

0xdb067026…9eb8

0x1d1325…2305

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 0x1b5d2e607a…9999b5

← previous block·next block →recent activity