← previous blocknext block →recent activity

Analyzing

Block #74,761,119

26 transactions · 18 stateful · 2026-05-15 13:32:30 UTC

Parallelism

81/100

Blocked

44%

Avg conflicts / tx

0.54

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,761,119  ·  26 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

8 touches
6 conflicts

0xb9868b52…c77f

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xdc683230…6df3

0x34b655…2a6f

6 touches
3 conflicts

0x61181965…f997

0xd32edf…ff58

5 touches
3 conflicts

0x62d6e82b…a750

0x34b655…2a6f

4 touches
1 conflict

0x84fb2a36…db89

0x34b655…2a6f

4 touches
1 conflict

0x9b8800c1…ed12

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity