← previous blocknext block →recent activity

Analyzing

Block #74,744,983

19 transactions · 14 stateful · 2026-05-15 11:44:26 UTC

Parallelism

74/100

Blocked

43%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,744,983  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x6b319071…a105

0xc8689a…ee79

8 touches
6 conflicts

0x9ae48cc5…1b29

0x065c9d…c394

8 touches
6 conflicts

0x3e4b8d9f…b8a7

0x5d823e…89c6

8 touches
6 conflicts

0xf0f673fd…37a7

0x5d823e…89c6

6 touches
3 conflicts

0x765c236f…ff45

0x2a68ba…90c5

6 touches
3 conflicts

0x348fda08…7e96

0x065c9d…c394

6 touches
3 conflicts

0x5b3dfef8…a676

0x5d823e…89c6

6 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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity