← previous blocknext block →recent activity

Analyzing

Block #74,355,911

13 transactions · 10 stateful · 2026-05-13 16:25:10 UTC

Parallelism

77/100

Blocked

30%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,355,911  ·  13 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

0x47b807a2…3307

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x119cc9e1…c4a4

0x065c9d…c394

4 touches
1 conflict

0x7a0f243e…fc2e

0x065c9d…c394

2 touches
0 conflicts

0x9eae85b9…7e16

0x065c9d…c394

2 touches
0 conflicts

0xa141d49c…f4e6

0x065c9d…c394

2 touches
0 conflicts

0xc04e953d…6d3f

0x065c9d…c394

2 touches
0 conflicts

0xe063b94e…3a0a

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 0x47b807a243…c53307

← previous block·next block →recent activity