← previous blocknext block →recent activity

Analyzing

Block #75,678,859

10 transactions · 9 stateful · 2026-05-19 19:50:24 UTC

Parallelism

80/100

Blocked

22%

Avg conflicts / tx

0.3

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,678,859  ·  10 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

0x23a320fb…cbd7

0x34b655…2a6f

4 touches
1 conflict

0x3c83275e…d7c2

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf853eb8e…4027

0x34b655…2a6f

4 touches
1 conflict

0xc6417de0…2191

0xc8689a…ee79

4 touches
1 conflict

0x1c913164…5c2e

0x34b655…2a6f

4 touches
1 conflict

0x9be2b99a…a959

0x34b655…2a6f

2 touches
0 conflicts

0x0d5dba7b…bd28

0xea1b8e…c5ec

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 0x23a320fbfb…26cbd7

← previous block·next block →recent activity