← previous blocknext block →recent activity

Analyzing

Block #74,307,361

9 transactions · 9 stateful · 2026-05-13 11:02:19 UTC

Parallelism

67/100

Blocked

33%

Avg conflicts / tx

0.67

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,307,361  ·  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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x6a2aae37…1240

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x37b6ec9b…1a36

0x065c9d…c394

2 touches
0 conflicts

0x428f7623…208c

0x065c9d…c394

2 touches
0 conflicts

0x5228e147…6819

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