← previous blocknext block →recent activity

Analyzing

Block #74,433,434

17 transactions · 12 stateful · 2026-05-14 01:01:16 UTC

Parallelism

82/100

Blocked

33%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,433,434  ·  17 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

0x99d40117…9c5b

0xd32edf…ff58

5 touches
3 conflicts

0x4f4bdabd…ffba

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0x8e80434a…a96d

0x0555e3…2b9c

2 touches
0 conflicts

0xe7ae9f8b…fc06

0x065c9d…c394

2 touches
0 conflicts

0xffe431af…8faa

0x065c9d…c394

2 touches
0 conflicts

0x46cb45de…a566

0x188d58…ea8e

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

3 conflicts on slot 0x99d4011709…3b9c5b

← previous block·next block →recent activity