← previous blocknext block →recent activity

Analyzing

Block #74,040,367

14 transactions · 10 stateful · 2026-05-12 05:26:16 UTC

Parallelism

71/100

Blocked

30%

Avg conflicts / tx

0.29

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,040,367  ·  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

0x4ee3f737…ebf8

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x0b390c61…dc07

0x065c9d…c394

2 touches
0 conflicts

0x4d6dfe95…3d80

0x065c9d…c394

2 touches
0 conflicts

0xb0f0dc94…e1d4

0x065c9d…c394

2 touches
0 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

2 touches
0 conflicts

0xc4917d1f…8397

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: 0xd32edf66…9fff58

3 conflicts on slot 0x4ee3f73737…29ebf8

← previous block·next block →recent activity