← previous blocknext block →recent activity

Analyzing

Block #74,439,433

15 transactions · 11 stateful · 2026-05-14 01:41:10 UTC

Parallelism

87/100

Blocked

36%

Avg conflicts / tx

0.27

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,439,433  ·  15 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x3eaded6f…ef38

0x065c9d…c394

3 touches
1 conflict

0x9ce504f9…e3f1

0xd32edf…ff58

3 touches
1 conflict

0x76e559a4…77fb

0x2a68ba…90c5

2 touches
0 conflicts

0xaeb5864c…7679

0x2a68ba…90c5

2 touches
0 conflicts

0x264c6e4e…cbb6

0x3bd359…433a

2 touches
0 conflicts

0x51ca3051…0972

0x3bd359…433a

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

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity