← previous blocknext block →recent activity

Analyzing

Block #74,490,583

11 transactions · 9 stateful · 2026-05-14 07:21:34 UTC

Parallelism

82/100

Blocked

11%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,490,583  ·  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

0xa0d06272…7893

0x065c9d…c394

4 touches
1 conflict

0x05e88e69…d6e9

0x065c9d…c394

3 touches
1 conflict

0xcd735781…7cdf

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x0dec7e8b…df6d

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x6bd6a013…78f6

0x065c9d…c394

2 touches
0 conflicts

0x72535002…23b2

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 0xa0d06272df…387893

← previous block·next block →recent activity