← previous blocknext block →recent activity

Analyzing

Block #74,762,709

27 transactions · 16 stateful · 2026-05-15 13:43:12 UTC

Parallelism

85/100

Blocked

38%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,762,709  ·  27 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xac298654…49b9

0xd32edf…ff58

7 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x2b24729f…41c0

0x34b655…2a6f

4 touches
1 conflict

0x1da1c6cb…bb3f

0x34b655…2a6f

4 touches
1 conflict

0x46e2bb67…d8b3

0x34b655…2a6f

4 touches
1 conflict

0x4b52d0b9…2b40

0x34b655…2a6f

4 touches
1 conflict

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

0xb9868b52…c77f

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

6 conflicts on slot 0xac298654ba…8e49b9

← previous block·next block →recent activity