← previous blocknext block →recent activity

Analyzing

Block #74,771,600

40 transactions · 26 stateful · 2026-05-15 14:42:47 UTC

Parallelism

88/100

Blocked

38%

Avg conflicts / tx

0.38

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,771,600  ·  40 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

0x1f853e78…1967

0xd32edf…ff58

7 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x18aed20c…48f3

0x000000…012a

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf8ed3fc0…b190

0x065c9d…c394

4 touches
1 conflict

0x4dd1db39…a994

0x188d58…ea8e

4 touches
1 conflict

0x4dd1db39…a996

0x188d58…ea8e

4 touches
1 conflict

0x765c236f…ff45

0x2a68ba…90c5

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: 0xd32edf66…9fff58

6 conflicts on slot 0x1f853e7872…731967

← previous block·next block →recent activity