← previous blocknext block →recent activity

Analyzing

Block #74,250,701

9 transactions · 8 stateful · 2026-05-13 04:45:28 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

0.67

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,250,701  ·  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

0x6f6353ca…f417

0x065c9d…c394

4 touches
1 conflict

0x8ffb4fab…76f8

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xf4659af6…0446

0x065c9d…c394

4 touches
1 conflict

0xcf3283ba…c9fa

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xa9b92643…5fa4

0x065c9d…c394

3 touches
1 conflict

0xc2df5809…eabb

0x065c9d…c394

3 touches
1 conflict

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

1 conflict on slot 0x6f6353ca63…eef417

← previous block·next block →recent activity