← previous blocknext block →recent activity

Analyzing

Block #74,509,079

11 transactions · 8 stateful · 2026-05-14 09:25:15 UTC

Parallelism

82/100

Blocked

25%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,509,079  ·  11 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

0x81f76c8c…a0c7

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0a7a3fd1…c7a2

0x065c9d…c394

3 touches
1 conflict

0x50918a06…d509

0x065c9d…c394

3 touches
1 conflict

0x7f8b7547…30ca

0x065c9d…c394

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0xf0b9e18d…eac7

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 0x81f76c8cfd…eba0c7

← previous block·next block →recent activity