← previous blocknext block →recent activity

Analyzing

Block #74,489,230

14 transactions · 12 stateful · 2026-05-14 07:12:33 UTC

Parallelism

71/100

Blocked

25%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,489,230  ·  14 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x7850d92a…7290

0x065c9d…c394

4 touches
1 conflict

0xf9efeb89…bcaf

0x065c9d…c394

3 touches
1 conflict

0x09a0fd06…369d

0x065c9d…c394

2 touches
0 conflicts

0x0d83c0ff…7e40

0x065c9d…c394

2 touches
0 conflicts

0x89292a99…c90e

0x065c9d…c394

2 touches
0 conflicts

0x8d946603…1a81

0x065c9d…c394

2 touches
0 conflicts

0x03622417…0bd6

0x2880ab…7b43

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity