← previous blocknext block →recent activity

Analyzing

Block #74,040,169

9 transactions · 9 stateful · 2026-05-12 05:24:57 UTC

Parallelism

56/100

Blocked

33%

Avg conflicts / tx

0.78

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,040,169  ·  9 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

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x1db883d1…af47

0x065c9d…c394

2 touches
0 conflicts

0x2397587f…0cd8

0x065c9d…c394

2 touches
0 conflicts

0xb46d7ce3…a6a0

0x065c9d…c394

2 touches
0 conflicts

0xc4860c26…f0f8

0x065c9d…c394

2 touches
0 conflicts

0xdef6bfa1…4383

0x065c9d…c394

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity