← previous blocknext block →recent activity

Analyzing

Block #74,722,543

14 transactions · 14 stateful · 2026-05-15 09:14:33 UTC

Parallelism

64/100

Blocked

36%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,722,543  ·  14 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x41755291…977f

0x065c9d…c394

8 touches
6 conflicts

0x42b09515…7234

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x00000000…0000

0xdf8787…c878

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0x00000000…0019

0x1b6862…e19c

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