← previous blocknext block →recent activity

Analyzing

Block #74,041,529

35 transactions · 25 stateful · 2026-05-12 05:33:59 UTC

Parallelism

80/100

Blocked

40%

Avg conflicts / tx

0.63

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,041,529  ·  35 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x0b390c61…dc07

0x065c9d…c394

12 touches
15 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0xf6cc7de8…0b4a

0x3bd359…433a

4 touches
1 conflict

0x2e2214a9…fe0d

0x5d823e…89c6

4 touches
1 conflict

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

15 conflicts on slot 0x0b390c6160…02dc07

← previous block·next block →recent activity