← previous blocknext block →recent activity

Analyzing

Block #74,598,753

39 transactions · 26 stateful · 2026-05-14 19:28:34 UTC

Parallelism

85/100

Blocked

50%

Avg conflicts / tx

0.56

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,598,753  ·  39 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xbbee74c2…567a

0x065c9d…c394

8 touches
6 conflicts

0x24968e6d…0132

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xe6455d1f…1029

0x754704…b603

6 touches
3 conflicts

0x12309510…0ac2

0x000000…012a

6 touches
3 conflicts

0x0d0b2509…074d

0x3bd359…433a

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xd77fdad5…2753

0xd32edf…ff58

5 touches
3 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

6 conflicts on slot 0xbbee74c2e7…6e567a

← previous block·next block →recent activity