← previous blocknext block →recent activity

Analyzing

Block #74,765,326

37 transactions · 24 stateful · 2026-05-15 14:00:42 UTC

Parallelism

89/100

Blocked

38%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,765,326  ·  37 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

0xf448c22d…911f

0xd32edf…ff58

7 touches
6 conflicts

0xb9868b52…c77f

0x34b655…2a6f

6 touches
3 conflicts

0x49f69157…4445

0x34b655…2a6f

6 touches
3 conflicts

0x7b6d2deb…dde0

0x34b655…2a6f

6 touches
3 conflicts

0xca0fef1c…b548

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x4a8069e8…67cc

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 0xf448c22d55…9f911f

← previous block·next block →recent activity