← previous blocknext block →recent activity

Analyzing

Block #74,538,436

32 transactions · 21 stateful · 2026-05-14 12:43:12 UTC

Parallelism

78/100

Blocked

38%

Avg conflicts / tx

0.72

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,538,436  ·  32 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

0xa1087a5c…66c4

0x754704…b603

12 touches
15 conflicts

0x2471e9b0…0e94

0x065c9d…c394

10 touches
10 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

9 touches
10 conflicts

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x91df3080…5a20

0x754704…b603

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6e

0x188d58…ea8e

4 touches
1 conflict

0xaeb5864c…7679

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: USDC (USDC)

15 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity