← previous blocknext block →recent activity

Analyzing

Block #75,469,075

18 transactions · 16 stateful · 2026-05-18 20:22:14 UTC

Parallelism

72/100

Blocked

50%

Avg conflicts / tx

0.78

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,469,075  ·  18 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

0xe1e41849…9772

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x5086c64a…28ba

0x34b655…2a6f

8 touches
6 conflicts

0xc166a323…1f33

0x34b655…2a6f

6 touches
3 conflicts

0x81a7ba4d…8c4b

0x23c26b…7777

4 touches
1 conflict

0x408e66bb…3d6b

0x34b655…2a6f

4 touches
1 conflict

0x53b4ef2b…8a05

0x34b655…2a6f

4 touches
1 conflict

0xb245fe36…d765

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

6 conflicts on slot 0xe1e418494f…f99772

← previous block·next block →recent activity