← previous blocknext block →recent activity

Analyzing

Block #74,571,949

9 transactions · 8 stateful · 2026-05-14 16:29:13 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,571,949  ·  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

0x24968e6d…0132

0x065c9d…c394

6 touches
3 conflicts

0x72830c21…da6e

0x065c9d…c394

3 touches
1 conflict

0xe3cc63ba…966d

0x065c9d…c394

3 touches
1 conflict

0x0897f1fe…9ce6

0x065c9d…c394

3 touches
1 conflict

0x62a2f515…13a8

0x065c9d…c394

3 touches
1 conflict

0x61a9d744…1242

0x065c9d…c394

2 touches
0 conflicts

0x64caffa7…e4df

0x065c9d…c394

2 touches
0 conflicts

0xfc31371c…659a

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

3 conflicts on slot 0x24968e6db4…f00132

← previous block·next block →recent activity