← previous blocknext block →recent activity

Analyzing

Block #74,328,808

9 transactions · 7 stateful · 2026-05-13 13:24:57 UTC

Parallelism

67/100

Blocked

29%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,328,808  ·  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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x2983ff4e…7081

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x2b8d43a2…a406

0x065c9d…c394

2 touches
0 conflicts

0x3dbedbde…cf04

0x065c9d…c394

2 touches
0 conflicts

0x716a4e0f…544a

0x065c9d…c394

2 touches
0 conflicts

0x995e8f22…9f21

0x065c9d…c394

2 touches
0 conflicts

0xa6b563f1…1793

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 0x0000000000…00003d

← previous block·next block →recent activity