← previous blocknext block →recent activity

Analyzing

Block #74,489,276

9 transactions · 7 stateful · 2026-05-14 07:12:52 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,489,276  ·  9 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

0x457bd5fb…f1f4

0x065c9d…c394

4 touches
1 conflict

0x41c3b079…4a89

0x065c9d…c394

3 touches
1 conflict

0x9e8ba70f…12b4

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x01854207…b5a0

0x065c9d…c394

2 touches
0 conflicts

0x1cc5411d…dda3

0x065c9d…c394

2 touches
0 conflicts

0x4a6ea76e…e52f

0x065c9d…c394

2 touches
0 conflicts

0xc8880139…2cef

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 0x457bd5fb24…04f1f4

← previous block·next block →recent activity