← previous blocknext block →recent activity

Analyzing

Block #74,527,196

9 transactions · 7 stateful · 2026-05-14 11:27:19 UTC

Parallelism

67/100

Blocked

29%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,527,196  ·  9 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x8c1fef56…eb37

0x065c9d…c394

3 touches
1 conflict

0x0233527f…0f25

0x065c9d…c394

3 touches
1 conflict

0x5d39cdb8…bc28

0x065c9d…c394

2 touches
0 conflicts

0x5e385b79…fc27

0x065c9d…c394

2 touches
0 conflicts

0x759028a1…cc76

0x065c9d…c394

2 touches
0 conflicts

0xc5b778d2…a901

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity