← previous blocknext block →recent activity

Analyzing

Block #74,259,929

7 transactions · 5 stateful · 2026-05-13 05:46:46 UTC

Parallelism

71/100

Blocked

20%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,259,929  ·  7 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x1d05b98d…6ec2

0x065c9d…c394

4 touches
1 conflict

0x1ec1c45d…875c

0x065c9d…c394

3 touches
1 conflict

0x9147e0ff…4a19

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x0fa2fffc…9bb6

0x065c9d…c394

2 touches
0 conflicts

0x24968e6d…0132

0x065c9d…c394

2 touches
0 conflicts

0x4efd1083…b764

0x065c9d…c394

2 touches
0 conflicts

0x69657e0d…3c62

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

1 conflict on slot 0x1d05b98de8…d26ec2

← previous block·next block →recent activity