← previous blocknext block →recent activity

Analyzing

Block #75,517,083

29 transactions · 17 stateful · 2026-05-19 01:49:31 UTC

Parallelism

83/100

Blocked

29%

Avg conflicts / tx

0.38

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,517,083  ·  29 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xcab72563…329a

0x34b655…2a6f

8 touches
6 conflicts

0x7151b1ad…4520

0x34b655…2a6f

6 touches
3 conflicts

0xd6d040d9…9ae3

0x34b655…2a6f

6 touches
3 conflicts

0x4f4bdabd…ffba

0x34b655…2a6f

4 touches
1 conflict

0x5b6af007…0f35

0x34b655…2a6f

4 touches
1 conflict

0x678143da…dc6b

0x34b655…2a6f

4 touches
1 conflict

0x75feba9b…62b8

0x34b655…2a6f

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity