← previous blocknext block →recent activity

Analyzing

Block #74,956,337

16 transactions · 13 stateful · 2026-05-16 11:16:01 UTC

Parallelism

75/100

Blocked

46%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,956,337  ·  16 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

0x3aadd4ed…869e

0xd32edf…ff58

7 touches
6 conflicts

0x765c236f…ff45

0x2a68ba…90c5

6 touches
3 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x3e49348b…9445

0x34b655…2a6f

4 touches
1 conflict

0xdbb23ac1…055c

0x34b655…2a6f

4 touches
1 conflict

0x7e1ff805…6d4c

0x065c9d…c394

3 touches
1 conflict

0x89afbd43…323a

0x065c9d…c394

3 touches
1 conflict

0x116ad300…d91d

0x065c9d…c394

3 touches
1 conflict

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

6 conflicts on slot 0x3aadd4ed01…41869e

← previous block·next block →recent activity