← previous blocknext block →recent activity

Analyzing

Block #74,359,390

13 transactions · 9 stateful · 2026-05-13 16:48:18 UTC

Parallelism

77/100

Blocked

22%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,359,390  ·  13 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

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x6237189d…89e1

0x065c9d…c394

2 touches
0 conflicts

0x71b464ed…c90c

0x065c9d…c394

2 touches
0 conflicts

0x9e6af916…1ae3

0x065c9d…c394

2 touches
0 conflicts

0xba34589d…0516

0x065c9d…c394

2 touches
0 conflicts

0xdf16d830…225d

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